Skip to main content

Trigger nodes

Trigger nodes start a flow when a campaign event occurs. Every flow needs at least one trigger. Trigger nodes don't require additional configuration. Add the trigger to the canvas, then connect it to the next node.

Trigger node examples

Participant Created​

Starts the flow when a participant joins the campaign for the first time. This can happen when you import a contact list or add a participant through the API.

Use this trigger to start an onboarding or outreach sequence as soon as a contact is added.

Participant Updated​

Starts the flow when any field in the participant record changes.

Use this trigger to react to data changes. For example, restart a flow when a key attribute changes after a communication ends.

Uploads and API calls can also update existing participants. If an imported row matches an existing participant, the system triggers Participant Updated instead of Participant Created.

Communication Ended​

Starts the flow when a communication session between a participant and an agent closes.

Use this trigger to process the outcome of a completed conversation. For example, check the result recorded by the agent, then schedule a follow-up or mark the participant as done.

Communication Updated​

Starts the flow when the status or data of an existing communication changes.

Use this trigger to react to mid-communication events. For example, take action when a scheduled communication becomes active or fails.

Incoming Session​

Starts the flow when an inbound message or session arrives from a participant on any configured channel.

Use this trigger to handle participant-initiated contact. For example, route an inbound message based on the participant's current status.

From Another Flow​

Starts the flow when another flow in the same campaign sends a participant through a To Another Flow action.

Use this trigger to create reusable subflows that other flows can call.

Was this article helpful?