Workflow Endpoint Error
# support
d
I updated my workflow API request endpoint, then tried saving changes, but it kept returning this error message. What could be the cause, and how can I resolve this? https://cdn.discordapp.com/attachments/1382761389533302864/1382761389889683618/image.png?ex=684c5465&is=684b02e5&hm=fcfddbede1aa59d64ecb4bc76b39a39aa47e4db4b5655fd057ad4e9a297c7ecf&
v
The error occurs because the
hooks
property is set on a node type that does not support it.
To resolve this, edit your workflow and remove the
hooks
property from any node except those that explicitly support hooks (like
ApiRequest
or
Gather
nodes). For example, your node should look like this:
Copy code
json
{
  "type": "conversation",
  "name": "My Node"
  // No "hooks" property here
}
After removing unsupported
hooks
, try saving again. Sources: - [Vapi Workflows Documentation](https://docs.vapi.ai/workflows) - [Vapi Changelog Feb 4, 2025](https://docs.vapi.ai/changelog/2025/2/4) - [Vapi API Reference: Create Workflow](https://docs.vapi.ai/api-reference/workflow/workflow-controller-create)
d
it's the url I'm trying to update from https://proofprep.vercel.app/api/vapi/generate to https://proofprep.com/api/vapi/generate Create specific values that get sent in the API request body string role {{ role }} string type {{ type }} string level {{ level }} string amount {{ amount }} string userid {{ userid }} string techstack {{ techstack }}
c
Hey! To help track down this issue, could you share: - The workflow ID This would really help us figure out what went wrong!
d
Here it's f9eafc-cbb-4f55-9f66-74390658ac14
@Shubham Bajaj ?
c
Hey, I looked into your workflow config, and I couldn't find anything wrong. I'll suggest you recreate it, if possible. If not, then give me some more time to take a look at it again later.
Hey @druxamb.base.eth, I found the issue when you create workflows using the API. Currently, it adds all the features to each node of the workflows, and there's a discrepancy between workflows created from the Dashboard and the API, which results in this issue. That's why it's best to create them using the Dashboard for now.
3 Views