Brightspot CMS
The Brightspot CMS integration is how an automation reacts to and acts on content in a connected CMS. It is the integration most automations are built around: a content event starts the flow, and content operations carry it out.
What it gives you
| Node | What it does |
|---|---|
| Content trigger | Superseded by the built-in Content trigger with a Brightspot connection: starts the automation when a content event occurs—published, revised, transitioned, archived, and more. |
| Content action | Superseded by the built-in Content Edit action with a Brightspot connection: publish, save, archive, delete, restore, transition, comment, or complete a work stream item. |
| Content Query action | Superseded by the built-in Content Query with a Brightspot connection: a query or a saved work stream, for a flow to run across. |
| Content Fetch action | Superseded by the built-in Content Fetch with a Brightspot connection. |
| Content Script action | Superseded by the built-in Script with a Brightspot connection, whose dari SDK then describes the connected CMS's content model. |
| Remote AI Agent action | Superseded by the built-in AI Agent with a Brightspot MCP server: hands a task to the connected CMS's own AI agent, which does the work with that CMS's tools. |
What it needs
A Brightspot connection. Every node above names one, and the connection decides which CMS the node acts on, which sites it may touch, and whose permissions it acts with.
The CMS you connect to must have the Esca Automations server module installed before connecting works—an administrator task. The connection also reports which version of that module the CMS is running, because some nodes need capabilities a later version added.
Working with revisions needs server module release 1.13.0 or later: a Content trigger's events naming the revision they are about, an On Demand button that runs on the revision the editor has open, a Content Fetch or Content Compare of a revision or version, and a Content Edit action that saves into, publishes, moves or discards a revision. With an earlier module, a node flags the revision settings that CMS can't honour, and a step that names a revision is refused with the release it needs rather than run against the content itself.
Running an automation from a content edit page
The built-in Content trigger's On Demand event, with a Brightspot connection, registers the automation on a content type in the connected CMS, which puts a button on that content's edit page. An editor can then run the automation on the asset they are looking at, without opening the flow editor.