Pappumaster
12/15/2025, 9:23 PMPappumaster
12/15/2025, 9:24 PMVapi Support Bot
12/15/2025, 9:24 PMcredentialId is not in the correct format. To fix this, go to the Vapi dashboard, create a new Custom Credential, and copy the generated credential ID (e.g., cred_abc123). Then, update your API node configuration like this:
json
{
"server": {
"url": "https://your-server.com/webhook",
"credentialId": "cred_abc123"
}
}
This should resolve the "credentialId must be a UUID" error. For more details, see the [Vapi server authentication documentation](https://docs.vapi.ai/server-url/server-authentication).
Source:
- [Server authentication | Vapi Docs](https://docs.vapi.ai/server-url/server-authentication)Vapi Support Bot
12/15/2025, 9:25 PMcredentialId is either left empty (if not required) or set to a valid UUID (e.g., 123e4567-e89b-12d3-a456-426614174000).
If you see a credential or server field, clear it or select a valid credential from the dropdown, then try saving again.
This error usually means a required ID is missing or incorrectly formatted—fixing it should let you save your workflow.
For more details, review your node settings and check for required fields as suggested in the [debugging guide](https://docs.vapi.ai/debugging).
Source:
- [Debugging voice agents](https://docs.vapi.ai/debugging)Pappumaster
12/15/2025, 9:42 PMPappumaster
12/15/2025, 9:43 PMVapi Support Bot
12/15/2025, 9:43 PMjson
{
"server": {
"url": "https://your-server.com/webhook",
"credentialId": "cred_abc123"
}
}
Replace the URL and credentialId with your actual values, then save your workflow.
For more details, see the [API Request node documentation](https://docs.vapi.ai/workflows/nodes/api-request).
Sources:
- [API Request node documentation](https://docs.vapi.ai/workflows/nodes/api-request)
- [Server authentication | Vapi Docs](https://docs.vapi.ai/server-url/server-authentication)Pappumaster
12/15/2025, 9:44 PMVapi Support Bot
12/15/2025, 9:45 PMPappumaster
12/15/2025, 9:53 PMVapi Support Bot
12/15/2025, 9:54 PMPappumaster
12/16/2025, 8:35 AMVapi Support Bot
12/16/2025, 8:36 AMPappumaster
12/16/2025, 8:51 AMPappumaster
12/16/2025, 8:51 AMVapi Support Bot
12/16/2025, 8:52 AMPappumaster
12/16/2025, 8:55 AMVapi Support Bot
12/16/2025, 8:56 AMcredentialId must be a UUID error.
If the error still appears, double-check that no other nodes (especially tool nodes) are present, even if they're not visible.
For more details, see the [server authentication guide](https://docs.vapi.ai/server-url/server-authentication).
Source:
- [Server authentication | Vapi Docs](https://docs.vapi.ai/server-url/server-authentication)Pappumaster
12/16/2025, 8:57 AMVapi Support Bot
12/16/2025, 8:59 AMcred_abc123) and is selected in the API node's "Server" section.
If the credentialId looks correct and the error persists, this may be a platform issue—please contact Vapi support with your workflow details and a screenshot of your Custom Credential for further assistance.
For reference, credential IDs should look like:
json
"credentialId": "cred_abc123"
See the [server authentication guide](https://docs.vapi.ai/server-url/server-authentication) for more details.
Source:
- [Server authentication | Vapi Docs](https://docs.vapi.ai/server-url/server-authentication)Pappumaster
12/16/2025, 9:03 AMPappumaster
12/16/2025, 9:03 AMVapi Support Bot
12/16/2025, 9:04 AMcred_abc123), and confirm that this ID is selected in your API node's "Server" or "Authentication" section? This will help determine if the issue is with the credential format or selection.
Source:
- [Server authentication | Vapi Docs](https://docs.vapi.ai/server-url/server-authentication)Pappumaster
12/16/2025, 9:09 AMVapi Support Bot
12/16/2025, 9:11 AMcurl (replace <workflow_id>, <your_token>, and the JSON as needed):
bash
curl -X PATCH https://api.vapi.ai/workflow/<workflow_id> \
-H "Authorization: Bearer <your_token>" \
-H "Content-Type: application/json" \
-d '{ "nodes": [ /* your updated nodes here */ ] }'
This lets you edit the workflow JSON directly—see the [API reference](https://docs.vapi.ai/api-reference/workflow/workflow-controller-update) for details.
Source:
- [API Reference: Update Workflow](https://docs.vapi.ai/api-reference/workflow/workflow-controller-update)Pappumaster
12/16/2025, 9:17 AMVapi Support Bot
12/16/2025, 9:18 AM<workflow_id>, <your_token>, and the JSON as needed):
bash
curl -X PATCH https://api.vapi.ai/workflow/<workflow_id> \
-H "Authorization: Bearer <your_token>" \
-H "Content-Type: application/json" \
-d '{ "nodes": [ /* your updated nodes here */ ] }'
This will update your workflow directly via the API.
For more details, see the [API reference](https://docs.vapi.ai/api-reference/workflow/workflow-controller-update).
Source:
- [API Reference: Update Workflow](https://docs.vapi.ai/api-reference/workflow/workflow-controller-update)Pappumaster
12/16/2025, 9:20 AMVapi Support Bot
12/16/2025, 9:21 AMcurl command there to update your workflow via the API:
bash
curl -X PATCH https://api.vapi.ai/workflow/<workflow_id> \
-H "Authorization: Bearer <your_token>" \
-H "Content-Type: application/json" \
-d '{ "nodes": [ /* your updated nodes here */ ] }'
For more details, see the [API reference](https://docs.vapi.ai/api-reference/workflow/workflow-controller-update).
Source:
- [API Reference: Update Workflow](https://docs.vapi.ai/api-reference/workflow/workflow-controller-update)Pappumaster
12/16/2025, 9:25 AMPappumaster
12/16/2025, 9:26 AMVapi Support Bot
12/16/2025, 9:27 AMcredentialId field in your API node's server section. Here’s an example curl command (replace the placeholders with your actual values):
bash
curl -X PATCH https://api.vapi.ai/workflow/<workflow_id> \
-H "Authorization: Bearer <your_token>" \
-H "Content-Type: application/json" \
-d '{
"nodes": [
{
"type": "apiRequest",
"name": "My API Node",
"server": {
"url": "https://your-api.com/endpoint",
"credentialId": "cred_abc123"
}
// ...other node fields as needed
}
]
}'
Just replace "cred_abc123" with your actual credential ID and fill in your node details as needed.
See the [API reference](https://docs.vapi.ai/api-reference/workflow/workflow-controller-update) for more info.
Source:
- [API Reference: Update Workflow](https://docs.vapi.ai/api-reference/workflow/workflow-controller-update)Pappumaster
12/16/2025, 9:47 AMPappumaster
12/16/2025, 9:59 AMPappumaster
12/17/2025, 9:56 AMVapi Support Bot
12/17/2025, 9:57 AM"nodes.tool.server.credentialId must be a UUID"
- Steps you've already taken (custom credential creation, new workflow, etc.)
This will help the Vapi team investigate and reset your org's tool/server state as needed.
For reference, see the [server authentication documentation](https://docs.vapi.ai/server-url/server-authentication).
Source:
- [Server authentication | Vapi Docs](https://docs.vapi.ai/server-url/server-authentication)Chiranjeet Mishra
12/17/2025, 9:24 PM