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	Starts the automation when a content event occurs—published, revised, transitioned, archived, and more.
Content action	Operates on one asset: publish, save, archive, delete, restore, transition it through a workflow, post a comment, or mark it complete in a work stream.
Content Query action	Resolves a query or a saved work stream to a list of content, so a flow can run across a whole set of assets instead of reacting to one event.
Content Fetch action	Reads one asset by content id, or by a field the type uses as a unique key such as a slug or an external id.
Content Script action	Runs a script that knows the connected CMS's content model, so it can build and edit content with named types and fields.
Remote AI Agent action	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.

Running an automation from a content edit page

The Content trigger's On Demand event 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.