Zapier Automation with Keygen SH: Handling Invalid UUID Issues

Automating license creation with Keygen SH and Stripe via Zapier returns a 400 error from a UUID mismatch. Logs show ‘uniqueID’ as a string; how can I fix this?

{
  "info": {
    "uniqueID": "123-abc-xyz"
  },
  "issues": [
    {
      "error": "Invalid Parameter",
      "detail": "Received string instead of a UUID format",
      "location": "/entity/owner/id"
    }
  ]
}

I encountered a similar problem when developing my own automation workflow. The issue stemmed from passing a string that did not meet the strict UUID format expected by the API. In my case, I had to add an intermediary step in my Zap to reformat the input value into a proper UUID before sending it along. I modified my Zap configuration to transform the data accordingly using a custom script, which ensured that the value adhered to version 4 UUID standards. As a result, the error was resolved and the process ran smoothly.

hey, i got similar issues. for me, changing the input to a proper uuid fixed it. u might need a uu1 tool or so to generate a real uuid instead of using a plain string.