Triggers
A published workflow has exactly one trigger. Choose it according to the event that should start the work, then choose an object supported by the trigger selector.
| Trigger | When it starts | Example |
|---|---|---|
| Record created | A record is created in the selected object. | Create a follow-up Task for a new request. |
| Record updated | A record is updated, optionally requiring changes to selected fields. | Review a request when its status changes. |
| Manual record | An authorized user deliberately starts the published workflow for one selected record. | Process an existing request on demand. |
| Recurring | A published calendar has an eligible occurrence. | Create a daily reminder. See Schedules. |
Record updates and conditionsโ
Changed-field selection asks whether a selected field changed. A condition asks whether a value matches. If you want work only when a status changes to a particular value, combine a Record updated trigger watching that field with If/Else comparing the captured value. Connect the otherwise path to End.
When several changed fields are selected, a change to at least one matches the changed-field selection. An ordinary update to unrelated fields does not match it. Preview cannot establish a changed-field match from one record alone: that requires a real before-and-after event.
The input belongs to the runโ
Record triggers capture the record revision at admission. Later edits do not refresh that input. Use an explicit Read Record step if you need a later observation of the record.
Automatic runs are admitted with the record change. If that transaction rolls back, its workflow admissions roll back too. Admission or input-size limits can therefore prevent the record write; the write's error explains the problem.
Record writes made by workflow actions still emit ordinary record events and webhooks, but they do not automatically admit further workflows. Do not design a chain that depends on one workflow update triggering another.
Starting manuallyโ
A manual start requires an enabled, published Manual record workflow and access to the chosen record. Review the selected version and record before confirming. Another deliberate manual start is another run and can repeat its business effects.
Enabling a record workflow does not scan old records or replay events from its paused period. Trigger eligibility also differs from record-action eligibility: the trigger selector excludes built-in objects even where a record action supports them.
See Permissions, Data mappings, and the run API reference.