Docs
/
/
Platform
Send messages
Triggering workflows
From an event

Triggering workflows via an event

Learn more about how to trigger cross-channel notification workflows in Knock via CDP and webhook events.

Events from customer data platforms like Segment or direct HTTP webhook integrations trigger workflows.

Event-triggered workflows decouple notifications from your backend systems — enabling non-developers to set up and configure notifications based on business events in your product.

Event-triggered workflows require that you have one or more sources configured and connected to Knock.

Configuring an event trigger

#

You can create and manage event triggers for your workflows under Platform > Sources, or directly from the workflow builder when you click the trigger step.

From the trigger step detail view, if you have events connected to Knock you'll see the option to switch the trigger type to Event from the dropdown menu. Once here, you can select an event that will trigger this workflow when it's received. You can also map the critical fields needed to run a workflow to the fields that will be in the incoming event payload.

Frequently asked questions

#

Yes. Configuring an event trigger does not prevent you from triggering the workflow via the API. Both trigger methods work independently, so you can use event triggers to automate notifications from external sources while still calling the API directly when needed.

Yes, it's possible to override the default behavior of a source event trigger to point the trigger to a property on the event that resolves to a list of recipients.

Yes. You can halt the run from a wait for event step that listens for a second source event, or map a cancellation key on the event trigger and cancel the run through the API. See canceling event-triggered workflows for both patterns.

New chat