Automations

An automation starts contact journeys when a trigger matches. Draft preparation and content testing are available within plan limits; activation and execution require paid Marketing and current capacity.

Prepare the journey

Create an automation and add triggers and steps. The editor saves after a short idle interval; wait for confirmation. Drafts may contain incomplete references or values while you edit, but activation requires a valid definition and available resources.

Publish designs used by email actions and review data, consent and senders. Actual execution checks eligibility and capacity again; preview does not grant sending permission.

Choose triggers and reentry

Respond to contact creation or changes, audience entry or exit, external events and dates. Triggers are alternatives; when several match, their order determines which starts the journey. Configure enrollment and whether a contact may reenter after completion or enter only once.

For dates, check automation timezone, contact timezone use, annual or one-time repetition, offset and February 29 handling. A historical one-time date is distinct from an annual birthday. Queues can process late and calendar recovery is bounded.

Build actions and branches

• Send email uses a design publication and contact data at message acceptance.
• Update contact changes profile data without granting consent.
• Add to or remove from segment requires an assignment segment.
• Conditions separate matching and nonmatching routes.
• A/B split distributes by the configured percentage without automatically choosing a winner.
• Exit ends the current journey, including its branches and later steps.

Finishing a branch continues after its block unless Exit is used. Waits can last an interval, reach an instant, await a condition or await an event. Conditions and events require a timeout and outcome routes. Durations and timeouts accept integer seconds from 1 to 31,536,000.

Arbitrary code or HTTP actions, manual enrollment and indefinite waits are unsupported.

Simulate and activate

Simulation with a contact returns a trace without modifying profiles, performing actions or creating an actual journey. Use it to inspect conditions and data; message testing below checks email content.

Activation validates and pins a published version. Active automations cannot save changes. Pause to edit; Resume continues the previous publication and Activate publishes the draft. Resume does not publish new edits.

Review journeys and pauses

Inspect journeys and attempts from details. Email acceptance confirms Sendiro admission, not delivery. Pausing retains progress and waits; time continues and deadlines do not shift on resume.

Unsubscribing prevents future Marketing email, while permitted profile actions may continue. Archiving or deleting the contact cancels its journeys. Individual journey pause, restart or cancel controls are unavailable. Choose Archive from the three-dot menu on its card in the Automations library. Confirming stops the automation and cancels pending journeys; you do not need to pause it first.

Test the messages on one path

Test messages, in the trigger inspector, is also available on Free and uses an authorized Contact as recipient and personalization source. Inspect the path calculated from its data; explicitly select another condition or A/B branch when needed, which is marked as forced. Preview shows message order, omitted actions, missing data and required allowance. Confirm up to 5 messages on that path, with [Test i/n] subjects. Test other paths separately.

The flow, designs and data are frozen. Waits, business hours and commercial actions are omitted: no Contacts changes, webhooks, activation or real runs occur. This tests content, personalization and sequence; it does not certify triggers, timing or actual automation execution. Review per-message results and retry only eligible failures without duplicating accepted messages.