Workflow OrgId must be a UUID
# support
v
@amg It looks like the issue you're encountering is related to the
orgId
field within your workflow object. The error message indicates that the
orgId
must be a valid UUID, but in your payload, you're using a placeholder UUID (
00000000-0000-0000-0000-000000000000
), which is not a valid UUID for your organization. To resolve this error, you should replace the placeholder
orgId
with the actual UUID of your organization. You can usually find this in your account settings or in the details of your organization within the VAPI platform. Make sure that the UUID you use is the one that was assigned to your organization by VAPI. Here's what you should do: 1. Obtain the correct
orgId
from your VAPI account. 2. Replace the placeholder
orgId
in your payload with the correct UUID. If you're unsure where to find your organization's UUID or if you continue to experience issues after updating the
orgId
, please reach out to support for more assistance.
You can continue this conversation by mentioning me in the message.
s
@amg could you please write your issue description and let me know what issue your facing currently?
a
Woops! I was trying to remove/"mark as resolved" because I thought the issue resolved itself. Turns out, I'm still having a little trouble. The issue I was having earlier is: I kept getting a 400 with the message "orgId must be a UUID" when using the workflow property on a transient assistant. 🤔 I have double-checked that my orgId is correct numerous times, so I'm certain that's not the issue. After testing for a while, that message went away and eventually I got a successful response (201) when performing a web call. The new problem I'm seeing is that when the call connects, the assistant only say the "firstMessage" then go silent. I'm not exactly sure what's causing this, but would be delighted to get some feedback.
@Shubham Bajaj Here's what my request payload looks like:
Copy code
POST 'https://api.vapi.ai/call/web'
=> 201

Request payload:
"assistant": {
    "name": "My agent",
    "transcriber": {
        "provider": "deepgram",
        "model": "nova-2",
        "language": "en-US"
    },
    "model": {
        "model": "custom",
        "provider": "vapi",
        "messages": [],
        "workflow": {
            "id": "<random-gen-uuid>",
            "orgId": "<org-uuid>",
            "createdAt": "2025-01-21T18:38:35.712Z",
            "updatedAt": "2025-01-21T18:38:35.712Z",
            "name": "workflow",
            "type": "workflow",
            "nodes": [
                {
                    "name": "node-1",
                    "type": "gather",
                    "instruction": "Greet the user and ask for their name."
                },
                {
                    "name": "node-2",
                    "type": "say",
                    "instruction": "My name is peter pan."
                }
            ],
            "edges": [
                {
                    "from": "node-1",
                    "to": "node-2"
                }
            ]
        }
    }
}
s
@amg As of now, workflows are not ready to be used for development and production use cases, so I suggest using assistants with prompting only instead. > The new problem I'm seeing is that when the call connects, the assistant only say the "firstMessage" then go silent. Could you share the call id related to this, so I can take a look?
2 Views