Support for workflow-level token restrictions?
# supports
Samyak Jain
08/16/2025, 5:14 PMHey folks đź‘‹
Quick question — I see token restrictions support things like allowedOrigins, allowedAssistantIds, and allowTransientAssistant.
Is there anything similar for workflows, like allowedWorkflowIds or allowTransientWorkflow? Do these fields already exist or are they not supported yet?
For example, something like:
const payload = {
orgId: process.env.ORG_ID,
token: {
tag: "public",
restrictions: {
enabled: true,
allowedOrigins: ["https://example.vapi.ai"],
// hypothetical workflow-level restrictions
allowedWorkflowIds: ["a1b2c3d4-5678-90ef-ghij-1234567890ab"],
allowTransientWorkflow: false
}
}
};
c
Chiranjeet Mishra
08/16/2025, 5:14 PMHi there,
Thank you for your message. Our team is currently out of the office. We operate Monday through Friday, from 9:00 AM to 8:00 PM Pacific Standard Time (PST).
We’ll get back to you as soon as possible during our normal business hours.
If your message is urgent, please mark it accordingly or include “URGENT” in the subject line, and we’ll do our best to respond promptly.
Warm regards,
Vapi
Customer Support Team
Chiranjeet Mishra
08/19/2025, 7:08 PMHi Samyak Jain,
For your inquiry about workflow-level token restrictions, Vapi currently supports the integration of OAuth 2 authentication for custom LLM models and webhooks. This can help manage access tokens and ensure secure authentication. You can configure authentication using the
authenticationPlan2 Views