Automations
Triggers
Every event that can start a workflow, and the data it carries.
How triggers enrol runs
An active workflow listens only inside its own client workspace. When a matching event arrives, Systemly applies the trigger-specific filter first, then every optional enrolment condition. A run is created only when all of those checks pass.
Contacts and pipeline triggers
Contact created
A contact is added manually, by import, form, booking, or another supported source.
Contact updated
A contact record is edited through the CRM service.
Tag added
A tag is attached to a contact. Filter to one tag or accept any tag.
Tag removed
A tag is removed from a contact. Filter to one tag or accept any tag.
Opportunity created
A deal is created, with its opportunity, pipeline, stage, and value identifiers in trigger data.
Opportunity updated
The non-stage details of an existing deal are updated.
Opportunity moved stage
A deal changes stage. Filter to a pipeline and, optionally, the destination stage.
Opportunity won
A deal enters a stage configured as won.
Opportunity lost
A deal enters a stage configured as lost.
Forms, bookings, and messages
Form submitted
A published form receives a valid submission. Filter to one form or accept any form.
Appointment booked
A booking is created. Trigger data includes the calendar, appointment, name, and start time.
Appointment cancelled
An appointment is cancelled in Systemly.
Message received
An inbound conversation message is stored. Data includes channel, sender, body, conversation, and message identifiers.
Social and payment triggers
Social post published
A queued social post finishes without a failed destination.
Social post failed
Publishing finishes with at least one failed destination.
Payment completed
A tracked payment completes. Amount, currency, description, and payment identifier are available.
Payment failed
A tracked payment fails. Trigger data includes its payment identifier and reported error.
Schedule and webhook choices
On a schedule
Starts one contactless run when its five-field UTC cron expression is due.
Webhook received
Reserved in the builder for inbound workflow webhooks; a public workflow trigger URL is not available yet.
For calls going out of a workflow, use the fully supported Call a webhookaction. See Scheduled workflows for cron syntax and contactless-run constraints.
Use trigger data
Every run stores an event topic plus the fields emitted by the source. In a condition, choose Trigger data and enter the field key, such as channel,formId, or amountCents. The run detail page shows the exact Trigger data object received, which is the best reference when building a condition.
Merge tags can also use {{event.topic}}. Unknown fields resolve to an empty value in templates and do not pass ordinary conditions.