Content Types
Structured shapes, defined once and then picked by name wherever an automation needs one. A content type is a named set of fields—an article summary, a translation request, a product record—and defining it here is what makes it available to a node that has to describe the data it expects or produces.
Why the page exists
Several nodes need to be told the shape of some data, not just its value. A trigger that accepts input has to say what that input looks like before anyone can fill it in; an AI step asked for structured output has to say what structure to fill. Rather than redeclaring those fields on every node, you define the shape once here and choose it by name.
Where that shows up:
| Where a type is chosen | What it does there |
|---|---|
| A trigger's Payload | Describes the input a run starts with. An on-demand trigger renders the type's own form for whoever presses the button; a schedule trigger delivers a fixed value of that type with every run. See Triggers. |
| An AI step's Payload Type | The structure the agent fills in as data, alongside its written answer. See the AI Agent action in Actions. |
In each of those places the picker offers the types defined on this page alongside the content types the platform already knows about, so a type defined here reads no differently from a built-in one.
One thing this page is not: it does not describe the content model of a CMS you have connected. A node that reads or writes content in a connected system—the content fetch, query, and save actions—asks that system for its own types over the connection. Those are configured on the node, not here. See Brightspot CMS.
The layout
The left rail lists your content types, ten at a time, alphabetically by name, with links above the list to page backwards and forwards through them:
| Control | What it does |
|---|---|
| Search | Matches types whose name contains what you type. Submit with Go, or let the list refresh as you type. |
| New | Opens an empty content type form. |
| The search icon | Opens the full CMS search, pre-filtered to content types, for when you want the sorting and filtering the search page offers. |
Selecting a type from the list opens its form on the right.
Defining a type
The form asks for a name and a list of fields, and each field has a name and a kind—plain text or rich text, a number, a checkbox, a date, a file, a choice from a list, a reference to other content, or a nested set of fields. Fields can be grouped into tabs and rows so a long type stays readable, and any of them can be marked required or repeatable. That field list is the shape: it is what a person sees when they fill the type in, and what an agent is asked to produce when it fills it in.
Beyond the fields, the form offers an icon for the type and a Developer tab holding the identifiers and rendering settings a developer may need. Neither is required to use a type in an automation.
A type that already does most of what you want can be copied rather than rebuilt—the copy opens as a new, unsaved type with the original's fields already in place, ready to be renamed and adjusted.
Changing a type changes it everywhere it is used. Renaming or removing a field that a node relies on will leave that node describing a shape that no longer exists, so check what depends on a type before reworking it.
Where to go next
- Triggers—how a trigger's payload reaches the rest of a run.
- Actions—what a step's output is, and how a structured output is referenced downstream.
- Brightspot CMS—the nodes that work with a connected system's own content model.