Content trigger
Starts the automation when a record changes. In the trigger picker it is Content, under General Triggers. With no connection it watches the records of the content types defined in this workspace on the Content Types page; with a Brightspot connection it watches content in that CMS instead, and its event list grows to everything that CMS raises. One trigger, one event picked from what the chosen store can deliver.
Fields
| Field | Required | Description |
|---|---|---|
| Connection | No | Leave empty to watch this workspace's records. Pick a Brightspot connection to watch content in that CMS. |
| Site | No | Shown only for a Brightspot connection: the site to act on. Blank means the connection's site when it pins exactly one, otherwise every site the connection reaches. |
| Types | No | Limit to specific content types. Leave it unset, and the placeholder reads Any Type, to match every type the store has. In a workspace, a type added later is covered without resaving the trigger. |
| Event | Yes | What to fire on. The workspace offers Published, Archived, Restored, Deleted and On Demand; a Brightspot connection adds Drafted, Revised, Merged, Scheduled, Unscheduled, Transitioned and Commented. Choosing one reveals whatever that event configures. |
| Fire Condition | No | A boolean expression evaluated against the trigger's output the moment an event arrives. When it is false, no run starts and nothing is counted. See Triggers. |
Events
| Event | Fires when | Its own fields |
|---|---|---|
| Published | Content is published. A workspace record has no publish step, so this is every save. | Only First—fire on a piece of content's first publish only, not on every republish. For a workspace record, its first save. |
| Drafted | A draft is created. | — |
| Revised | A revision is made to existing content. | — |
| Merged | A draft is merged. | — |
| Scheduled | Content is scheduled for publication. | — |
| Unscheduled | A scheduled publication is cancelled. | — |
| Transitioned | Content moves through a workflow. | Workflow—the workflow to watch, picked from the connected CMS. Transitions—which of that workflow's transitions to fire on. |
| Archived | Content is archived. | — |
| Restored | Archived content is restored. | — |
| Deleted | Content is deleted. | — |
| Commented | A comment is posted on content. | — |
| On Demand | An editor clicks a button on the content's edit page. | Display Name—the button's label, defaulting to the automation's name. Description—the line shown beside the button, defaulting to the automation's description. Cooldown—how long the button stays disabled for the same content after a run. Leave it blank or zero for no throttle. |
Every event exists once. The store says which it delivers, so a trigger moved from the workspace to a connection keeps its event when the connection has it.
What raises a workspace event
A workspace record fires the same events whether a person changed it or an automation did. Saving a record on its edit page raises Published; so does a Content action's Save. Archive, Restore and Delete work the same way, from the edit page or from the action. An automation can therefore start itself: a trigger on Published in an automation that saves the same type of record will fire on its own save. Guard against that with a condition around the save, a fire condition that ignores the automation's own changes, or a concurrency limit on the trigger.
On Demand, in more detail
On Demand is the one event nothing raises on its own: an editor decides when to press the button. In a workspace, the button appears in the Automations panel on the right rail of a record's edit page, for every record of a type the trigger matches; pressing it opens a popup that names the automation and the record and runs it. On a connected Brightspot CMS, saving the trigger registers the button there, and the connected CMS's own edit page shows it.
While a published automation has a revision in progress, the revision's trigger is listed too, badged Dry run, so you can rehearse a change against a real record without disturbing the live button.
Output
The event's payload—the affected content and the event's own metadata—plus a Content Edit URL that opens the content where it lives: this CMS for a workspace record, the connected CMS otherwise. The exact shape depends on the event, and later steps see that shape as soon as you pick one.
Deliveries
Every event the trigger receives is recorded on its Deliveries screen, from the node's menu, whether it started a run, was gated by the fire condition, or was skipped because the automation was off. A workspace event is recorded with the origin Event; a connected CMS's arrives as an inbound webhook, and can be replayed from there.