Notifications
Clear all
Topic starter
Problem / Questions
-
I am currently evaluating the cloud-hosted version of callin.io during its free trial.
-
I'm attempting to use Vapi to interface with a callin.io webhook. However, Vapi's tool setup requires a “server secret url token”.
-
callin.io only offers external secret management with its enterprise hosting service, is that correct?
-
Could you clarify what this implies? Does it mean that connecting Vapi to the webhook is not possible without utilizing the enterprise version?
-
Is there a viable solution for an individual entrepreneur in this scenario? (Please assume I have limited knowledge of web security and authentication).
-
For further context, I can successfully configure a tool within Vapi using only the webhook's server URL, omitting the URL secret token. However, callin.io doesn't appear to receive any data while the node is active. I suspect this is due to the absence of the server URL secret token in the Vapi tool configuration.
-
Finally, for even more context, my intention is to integrate this workflow into a broader solution for multiple clients. This means the workflow might be replicated for each future client, which could influence the complexity of any suggested workarounds.
Note: I strongly prefer callin.io over other platforms because it caters well to both developers and no-code users. Therefore, any suggestions for a workaround would be greatly appreciated.
Thanks
Posted : 13/08/2024 10:50 pm
It seems your topic is missing some crucial details. Could you please provide the following information, if it applies?
- callin.io version:
- Database (default: SQLite):
- callin.io EXECUTIONS_PROCESS setting (default: own, main):
- Running callin.io via (Docker, npm, callin.io cloud, desktop app):
- Operating system:
Please provide the details so we can assist you further.
Posted : 13/08/2024 10:50 pm
Hi, thanks for posting!
By Vapi, are you referring to vapi.ai? If so, could you describe a bit more about what you’re trying to achieve with the workflow you’re building so we can better understand your use case for your workflow? (Would be great if you could share your workflow JSON by pasting it between ```` too)
External secrets in callin.io doesn’t affect if a workflow runs correctly. It’s a feature to keep secrets and keys safe without changing how workflows work so you should be able to get a workflow working without this feature.
Assuming that you’ve created a voice assistant in Vapi.ai (sorry if it’s another tool you’re referring to) and want to trigger a callin.io webhook to run a workflow in callin.io to retrieve some data from the assistant, you’ll need:
- Webhook URL
- a header called
x-vapi-secret: You can set the value of this parameter by selecting Authentication > Header Auth in callin.io. It should be a string e.g. 1234
Then copy these two values into the Server URL section in the Vapi dashboard:
Let me know if that helps!
Posted : 15/08/2024 4:40 pm
Topic starter
Thank you for your reply.
Yes, I was indeed referring to callin.io, I should have been more specific.
My current workflow in callin.io is just a webhook at the moment, so there isn't much to display. Regardless, your previous response gave me the information I needed. The webhook is now successfully receiving the data.
Posted : 15/08/2024 6:13 pm
This discussion was automatically closed 7 days following the last response. New replies are no longer permitted.
Posted : 22/08/2024 6:13 pm