Stathis
12/10/2025, 12:13 AMVapi Support Bot
12/10/2025, 12:14 AMcredentialId field in your API Request node is set to a valid UUID (e.g., 123e4567-e89b-12d3-a456-426614174000).
json
"credentialId": "123e4567-e89b-12d3-a456-426614174000"
Double-check that you are not leaving this field blank or using a non-UUID value—use the actual credential UUID from your n8n or Vapi integration settings before saving the workflow.
For more details, see the [Workflows overview documentation](https://docs.vapi.ai/workflows/overview).
Source:
- [Workflows overview documentation](https://docs.vapi.ai/workflows/overview)Stathis
12/10/2025, 12:16 AMStathis
12/10/2025, 12:18 AMStathis
12/10/2025, 12:31 AMVapi Support Bot
12/10/2025, 12:31 AMcredentialId field in your workflow's API request node. In your JSON, if the credentialId is empty or not a valid UUID, you'll encounter the "each value in nodes.tool.server.credentialId must be a UUID" error when trying to save the workflow.
From your attached details, it appears that one instance of Credential ID is an empty string, while another is set to "924ee26d-5414-4959-81cf-a3da64c4b", which is a valid UUID format. To resolve the error, make sure that every credentialId field in your workflow is set to a valid UUID and not left empty. Double-check all nodes in your workflow to ensure there are no empty or invalid credentialId values.
If you update any empty or invalid credentialId fields to use the correct UUID, you should be able to save your workflow successfully.Stathis
12/10/2025, 12:34 AMStathis
12/10/2025, 12:34 AMVapi Support Bot
12/10/2025, 12:35 AMcredentialId fields in the raw data. Update any instance like this:
json
"credentialId": "your-valid-uuid-here"
Replace "your-valid-uuid-here" with the correct UUID from your integration settings, then re-import and save the workflow. This should resolve the error if a hidden or system node is missing a valid credential ID.
For more details, see the [API Request node documentation](https://docs.vapi.ai/workflows/nodes/api-request).
Source:
- [API Request node documentation](https://docs.vapi.ai/workflows/nodes/api-request)Chiranjeet Mishra
12/10/2025, 1:00 PMcredentialId field in your workflow's JSON is left empty or doesn't contain a valid UUID. To resolve this issue, please follow these steps:
1. **Export Your Workflow to JSON**: Go to your Vapi dashboard, export the workflow and download the JSON file.
2. Search for credentialId **Fields**: In the JSON file, look for any credentialId fields. These might appear in nodes or server settings.
3. **Update with Valid UUIDs**: Ensure every credentialId field is filled with a valid UUID. If you don't have one, you might need to create a custom credential in the Vapi dashboard and use its UUID.
Example credential in JSON:
json
"credentialId": "your-valid-uuid-here"
4. **Re-import and Save**: After updating the JSON, re-import the workflow back into Vapi and attempt to save.
Following these steps should help you save the workflow successfully. For more details, you can check the [API Request node documentation](https://docs.vapi.ai/workflows/nodes/api-request) or the [Workflows overview documentation](https://docs.vapi.ai/workflows/overview).