Skip to main content
POST
Fire a trigger
Every call starts a new workflow run and repeats the steps before the scheduler, including CRM writes and steps that consume a routing assignment. When you already have an outcome, reuse it instead of firing again.

Authorizations

Authorization
string
header
required

Organization API key, created in workspace settings (Settings → API Keys). Sent as Authorization: Bearer <key>. Shown once at creation; revocable and permission-scoped per key.

Path Parameters

trigger
string<uuid>
required

Trigger id from the list endpoint.

Body

application/json
email
string<email>
required

The lead being routed. Identity always comes from this field, never from responses. The connected form's email field is filled from it automatically.

responses
object

Form field values, keyed by field name from the list endpoint.

context
object

Web context you know about the lead. All fields optional. It becomes form submission data the workflow can reference and records as attribution on a booked meeting.

Response

Success

executionId
string<uuid>
required
outcome
object
required