Configure workflow triggers
Last updated: August 10, 2026
A trigger defines when and on what conditions a contact can enter a workflow.
Select a trigger
Open a new or existing workflow.
Select the trigger node at the top of the canvas.
Choose a trigger type.
Complete its configuration and select Save.
Select Update Workflow when editing an existing workflow.
Different trigger types
Trigger | Starts when | Channels | Important conditions |
|---|---|---|---|
Any Message | A contact sends any supported direct message | Instagram, Facebook | - |
Message Text | A direct message matches the configured text rule | Instagram, Facebook | Applies to new message events |
Comment Text | A comment matches the configured text rule | Instagram, Facebook | Applies to new comment events |
Any Comment | Any supported Instagram or Facebook comment arrives | Instagram, Facebook | Applies to new comment events |
Contact Tag | One of the tags is added to a contact | Instagram, Facebook | - |
Schedule | A periodic evaluation finds contacts matching every condition | Instagram, Facebook | Minimum interval is 30 minutes |
Trigger and action support must match for every selected channel. If one step is incompatible, channel selection will be blocked until you change the step or channel.
Configure Message or Comment text
Message Text and Comment Text use the same text operators.
Interface operator | Actual match | Example |
|---|---|---|
Equals | The complete incoming text equals one configured value, ignoring letter case |
|
Contains any of | The complete incoming text equals any one of the listed values, ignoring letter case | message must equal |
Contains any of the words within | The incoming text contains any configured word or phrase at a word boundary, ignoring letter case |
|
Add each text or keyword as its own value. Avoid using punctuation-only keywords and overlapping rules across active workflows unless multiple runs are intentional.
Configure Any Message
Any Message needs no text rule and starts for any supported incoming direct message.
This trigger can create a high number of runs. Before activation:
Confirm that another active workflow does not already react to the same messages.
Decide whether contacts may re-enroll.
Add a branch when only some messages should continue to actions.
Test non-text messages if the workflow depends on the incoming content.
Configure a Contact Tag trigger
Choose one of these operators:
Operator | Configuration | Starts when |
|---|---|---|
Equals | One tag | That tag is added to the contact |
Contains any of | Multiple tags | Any selected tag is added to the contact |
A contact merely retaining the tag does not create a new real-time tag event. To include contacts that already have the tag at first activation, review Enroll Existing Contacts.
Configure a Schedule trigger
A Schedule trigger evaluates matching contacts at an interval. It does not schedule a message for an exact clock time.
Enter an interval of at least 30 minutes, 1 hour, or 1 day.
Add one or more conditions.
Save the trigger.
Review the schedule-specific enrollment settings before activation.
Every configured condition must match the contact during an evaluation.
Condition | Operators and values | Matches contacts when |
|---|---|---|
Contact Tag | Equals one tag or contains any selected tag | The contact currently has the required tag |
Time Since Last Message Received | Greater than a positive number of seconds, minutes, hours, or days | The latest incoming message is older than the configured duration |
Time Since Last Message Sent | Greater than a positive number of seconds, minutes, hours, or days | The latest outgoing message is older than the configured duration |
Last Message Direction | Sent or Received | The contact's latest message direction matches |
Schedule evaluations exclude contacts that are marked as excluded from workflows.
Contacts assigned to Autopilot are excluded from scheduled enrollment.
Schedule timing depends on periodic processing. Treat the interval as the earliest evaluation cadence, not a guaranteed delivery time.
Understanding Existing Contact enrollment
Enroll Existing Contacts is evaluated when the workflow is activated for the first time.
Trigger | Existing-contact behavior |
|---|---|
Contact Tag | Can find contacts that already have the selected tag |
Message Text | Can use matching stored direct messages |
Any Message | Can use stored message activity when the feature is enabled |
Schedule | The schedule processor evaluates matching contacts; it does not bulk-start them during save |
Comment Text | Existing-comment enrollment is not supported; wait for a new matching comment |
Any Comment | Existing-comment enrollment is not supported; wait for a new comment |
Few things to note
Re-enrollment rules can block a contact that previously entered the workflow.
A standard workflow can skip a contact currently handled by Autopilot unless its eligible Autopilot Compatibility setting is enabled.
Comment triggers react to comments; message triggers react to direct messages.
Multiple active workflows can start from the same event when their trigger rules overlap.