Trigger

Overview

The System Event Trigger is the default starting point for automation flows that depend on state changes in internal records (such as in CRM) or redirect commands from the ecosystem itself. Its main function is to listen for specific events associated with the data lifecycle or receive "bridge" instructions coming from external relationship sequences and other competing automation flows.

Configuration Parameters

The trigger configuration defines the nature of the flow input. It is managed through the following main controls:

• Base Event Selection: Defines which data mutation will trigger the automation. Native events include:

  • Conversion: Triggered when a lead or contact performs a conversion action (e.g., form fill, material download).

  • Person created: Triggered immediately after a new contact record is inserted into the database.

  • Person updated: Activated when any field or property of an existing contact is modified.

  • Person deleted: Triggered when a record is removed from the system.

  • Person merged: Executed when two duplicate records are merged.

  • Person blocked: Triggered when communication or privacy restrictions are applied to the contact.

Visual Conditional Builder

The component has a block-structured visual rules engine to filter which records that generated the event will actually start the flow:

• AND Block: Groups criteria that must be simultaneously true. It is used to narrow the event (e.g., Event = Person created AND State = SP).

• OR Block: Groups alternative criteria. The flow will start if any of the inserted lines matches (e.g., Channel = WhatsApp OR Channel = Telegram).

• Add Condition Button: Allows nesting multiple complex logical blocks for advanced segmentations.

Special Operators and Trigger Sources

In addition to the manual and automatic registration events, this trigger responds to two special operational sources within the automation architecture:

• Trigger via Automation Sequence (CRM): The trigger acts as the receiving node for external campaigns or relationship sequences. When the lead reaches a certain stage in the CRM funnel, the CRM itself injects the contact directly into this trigger to start the secondary automation.

• Redirection via Bypass Component (goTo): It works as an anchoring point for process reuse. A flow "A" can use a component of type goTo (Go To) pointing to this trigger to transfer the customer journey to the current flow, without the need to duplicate code blocks.

Practical Examples

The table below demonstrates common scenarios for using this trigger in the ecosystem:

Selected Event	Configured Condition	Practical Use Case
Person created	None	Trigger an immediate welcome message for leads coming from ads.
Won card	None	Start the onboarding flow and access provisioning after purchase.
Person updated	Funnel Stage equal to Lost	Move the contact to a re-engagement sequence or send a satisfaction survey.
(None - External call)	Triggered via component goTo	Centralize the sending of invoices coming from 3 different sales flows in one place.