Skip to main content
Launch a published or draft workflow from a public HTTP trigger without turning this page into an API reference.

​
Prerequisites

  • A saved workflow draft.
  • An API key created in the Console and a telephony configuration for outbound calls.

​
Configure the trigger

  1. Add an API Trigger node and choose a descriptive trigger path.
  2. Keep the trigger enabled while testing; a disabled trigger returns not found.
  3. Copy the test or production URL shown on the node.
  4. Send a POST request with the required call destination and any initial context.
  5. Use the test URL for draft verification, then use the production URL after publishing.

​
Constraints and failure states

The trigger path is limited to 36 letters, numbers, hyphens, or underscores. Test mode runs the latest draft and falls back to the published agent when no draft exists; production runs the published agent. Requests require the X-API-Key header, and a selected telephony configuration must belong to the same organization.

​
Protect your data

Keep the API key server-side. Send only the initial context needed for the call and never place a real key in browser code, logs, or documentation examples.

Related topics

Editing a workflowWorkflow fundamentalsAdd an agent to a websiteGlobal nodeAgent node