I started experiencing this issue after creating a new tool in the workflow. Even if I make a minor change to the URL without modifying the credentials, saving still triggers this error. https://cdn.discordapp.com/attachments/1445018528146260109/1445018529668796487/image.png?ex=697c9a60&is=697b48e0&hm=2ec4423f923fa0f6e58c93bc114c650fb329e83b2cfc3cdbd1bb38e491dfba48&

To resolve the error, ensure your

credentialId

is a valid UUID as required by Vapi. Update your tool's server configuration like this:

json
"server": {
  "url": "https://your-api.com/tool-endpoint",
  "credentialId": "550e8400-e29b-41d4-a716-446655440000"
}

Replace the example UUID with your actual credential's ID from the Vapi dashboard. For more details, see the [Vapi server authentication documentation](https://docs.vapi.ai/server-url/server-authentication). Source: - [Vapi Server Authentication Documentation](https://docs.vapi.ai/server-url/server-authentication)

I'm also running into this issue. I can't save my workflow because of it.

Here's a workaround twhat wprked for me. You can create a tool for the API call and replace the API Call Node in your flow with the tool.

Same issue

Kindly checkout Vapi Squads ([https://vapi.ai/blog/introducing-squads](https://vapi.ai/blog/introducing-squads)). Vapi Workflows has been discontinued in favour of Squads. Squads is much more capable and simpler than workflows. Because Workflows is no longer actively supported, our ability to assist with Workflow related issues is limited. I am sorry for any inconvenience this may cause. Thank you

Maybe I'm not familiar enough with the capabilities of Squads, but aren't workflows and squads solving different problems? Regardless, this isn't really an adequate response if workflows are going to be left in the menu. They're completely unusable using the built in tools. Custom tools work fine, but new users won't know this.

That's a real bummer. I personally liked workflows. I could keep the conversation structured and could force tool calls before the conversation could move forward. I now have to go out and build a bunch of different agents to get it to function similarly. Workflows was my solution to customer verification.

Do you have any response to my concerns? https://discord.com/channels/1211482211119796234/1445018528146260109/1448753007503085774

workflow as a product is built out but we noticed that the LLM is not smart enough to act as an agent that can have awareness of current node instructions and meet conditions reliably. This is the pattern we found from our end, and we also found that customers are having better outcomes with squads for similar setups. So we are focusing more towards making the ergonomics of squads better.