Content trigger
Starts the automation when a content event occurs in a connected Brightspot CMS. In the trigger picker it is Content, under Integration Triggers.
Fields
| Field | Required | Description |
|---|---|---|
| Connection | Yes | The Brightspot connection whose CMS to watch. |
| Sites | No | Limit to specific sites. Leave it unset—the placeholder reads any site—to match content on every site the connection reaches. |
| Types | No | Limit to specific content types. Leave it unset, and the placeholder reads Any Type, to match content of every type. |
| Event | Yes | The content event to fire on. Choosing one reveals whatever that event configures (see below). |
Events
| Event | Fires when | Its own fields |
|---|---|---|
| Published | Content is published. | Only First—fire on a piece of content's first publish only, not on every republish. |
| 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 in the connected CMS. | 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. |
On Demand, in more detail
On Demand is the one event nothing in the CMS raises on its own: saving the trigger registers a button on the edit page of the content it matches, and an editor decides when to press it. Sites and Types decide where that button appears, exactly as they decide what the other events match—so an On Demand trigger with no types set puts the button on every content type.
Output
The event's payload—the affected content and the event's own metadata—plus a link to the content's edit page in the connected CMS. The exact shape depends on the event, and later steps see that shape as soon as you pick one.