Triggers and system blocks

Entry point of the workflow. Every workflow has exactly one entry: the first trigger selected when the workflow is created. Contacts enter the journey only through it.

Removes a contact from the workflow when needed, for example when the contact no longer matches the journey's goal. The contact stops moving through the workflow at this block.

Marks the successful end of the journey for a contact. Every workflow must end with this block, without exceptions, and each path in the workflow must lead to it.

Activates when a specific event (such as delivery, open, or click) occurs for a message sent using a selected template. Available for Email, SMS, WebPush, Telegram, and Viber templates.

Activates when a specific event occurs for a message from a selected one-time campaign. Available for Email, SMS, WebPush, Telegram, and Viber campaigns.

Activates when a specific event occurs for any message assigned a selected tag. Available for Email, SMS, WebPush, Telegram, and Viber messages.

Activates the moment a contact is added to the contact list via API, manual entry, file import, or another system trigger.

Activates when a contact enters or leaves a selected segment, for example after a variable update or data import. The block can be set to start the journey either when a contact is added to the segment or when a contact is removed from it. The "Also run for contacts already in this segment" checkbox lets contacts that were already in the segment before the workflow was launched start the journey as well.

Activates when a contact subscribes to or unsubscribes from a specific communication channel (Email, SMS, WebPush, Telegram, Viber) via a subscription form, an unsubscribe link, API, or manual action.

Activates when a custom event is fired for a contact via the API or an integration, signaling that a predefined action has occurred.