Incoming Message Step

The Incoming message step is available to For dialogs automations and creates a run after a matching message. Add it from the step catalog.

Choose Messages That Start A Run

Select the Incoming message step on the workflow. First use Message sender that starts the step to choose Customer, Operator, Agent, or Any sender. Then select the Which messages should start a run field. Three modes are available:

• All incoming messages starts the automation after every matching message;
• Contains keywords starts it only when the message matches a word or phrase from the list;
• The /start command begins with a prefix checks the platform start payload sent with a /start command or bot link.

For keyword matching, enter a phrase in the Words and phrases field and press Enter to turn it into a tag. You can paste several phrases separated by commas, semicolons, or line breaks, copy the whole list, and remove an individual tag. Up to 100 unique phrases are allowed. Matching is case-insensitive; the phrase must occur as a distinct sequence rather than as part of a longer word.

In Where to trigger, choose all dialogs, private dialogs only, or group dialogs only.

In Channels, select up to 50 required channels. If none are selected, the step applies to every project channel. An unavailable, deleted, or other-project channel blocks publication.

In keyword mode, add at least one phrase. The step does not pass validation with an empty list.

Start From A /start Parameter

Select The /start command begins with a prefix, then add one or more values in /start command prefixes. Enter only the parameter without /start, for example partner.

The partner prefix matches the partner and partner_123 payloads, but not partnership or partner-123. If several prefixes match, Senler uses the longest one. Matching is case-sensitive.

This lets different links or acquisition sources start different scenarios. The mode works only when the platform supplies start_payload; a regular text message such as /start partner does not replace it. Add at least one prefix because an empty list does not pass validation.

Store The Message Text

Enable Save message to a run variable, then use the variable field to select a Run, Lead, Dialog, or Project text variable. A Run variable receives the value at the start of the new run; a Lead, Dialog, or Project value is written before the run is created. Following steps can use it in a message or condition, for example.

Configure Repeated Starts

By default, repeated entry is enabled, and the previous active run of this automation for the same lead or dialog is cancelled before a new run starts.

• disable repeated entry when a new message should not create a run while the previous one is active;
• keep repeated entry enabled and disable ending previous runs when several runs may execute in parallel;
• keep both options enabled when a new run should replace the previous one.

Start From An Event

For an Event step, use Event that starts the step to choose a reaction being added or removed, a like being added or removed, or a lead being blacklisted. Its complete settings, repeated starts, and testing flow are covered in Event step.

Add A Continuation

A trigger cannot have incoming connections. Connect its output to the next step. If there is no continuation, validation returns a warning: the run will start and finish immediately.