Actions · Systemly

Communication actions

Send email

Sends through the workspace email provider to the contact's email address. Subject and plain-text body support merge tags, and can be copied in from an email template.

Send SMS

Sends up to 1,600 characters through the connected Twilio integration to the contact's phone number.

Call a webhook

Sends JSON to an HTTPS endpoint with POST, PUT, or PATCH, optional headers, and merge tags.

CRM and pipeline actions

Add tag

Adds the selected workspace tag to the run's contact.

Remove tag

Removes the selected workspace tag from the run's contact.

Assign user

Assigns the contact to a current member of the workspace.

Update contact

Sets configured contact fields after rendering merge tags. Empty rendered values are ignored.

Create opportunity

Creates a deal for the contact in the chosen pipeline and stage, with a templated title and fixed value.

Move pipeline stage

Moves the contact's newest open deal in the chosen pipeline to the selected stage.

Create task

Creates a task due 0 to 365 days from execution, optionally assigned and linked to the run's contact.

Flow-control actions

Wait

Pauses for 1 to 365 minutes, hours, or days, then resumes at the next step.

Only continue if

Checks an all-or-any condition group and ends the run normally when it does not pass.

A wait stores its resume time and releases the worker. It does not keep a browser request or process open for the duration.

Personalise actions with merge tags

Insert a value with double braces. Supported shortcuts in the builder include{{contact.firstName}}, {{contact.lastName}},{{contact.fullName}}, {{contact.email}},{{contact.phone}}, {{contact.businessName}},{{contact.leadSource}}, {{workspace.name}}, and{{event.topic}}.

Merge tags work in email and SMS content, task text, opportunity names, contact updates, webhook URLs, and webhook header values. They perform value substitution only: expressions and function calls are not executed. An unknown token becomes an empty string.

When an action is skipped

Contact actions skip when the run has no contact.
Email or SMS skips when the contact has no matching address or has opted out.
Assign user skips when the selected person is no longer a workspace member.
Move stage skips when the contact has no open deal in the selected pipeline.
Update contact skips when no non-empty, supported fields remain after rendering.

A skipped action is not a failed run. Its reason appears under that step in the run log, and execution continues unless the skipped step is a failed continue-if condition.

Webhook requests

The request body contains the workspace ID, contact ID, run context, and current contact data. Systemly sets JSON content headers and waits up to 15 seconds. A non-2xx response is a failed step, and up to 2 KB of the response is retained for the run log.