Integrations
Integrations connect an automation to the systems you already use. Each integration provides triggers, actions, or both, and most rely on a connection that holds the authentication. This page catalogs what each integration can do; for field-level detail, see the Reference.
Brightspot
Acts on content in a connected Brightspot CMS.
- Trigger—the Content trigger fires on a content event (published, revised, transitioned, archived, and more). See Triggers.
- Action—the Content action operates on a target asset, identified by its ID. Operations: Fetch, Publish, Save, Archive, Delete, Restore, Transition (move it through a workflow), Post Comment, and Complete Work Stream Item (mark it complete in a work stream).
- Content Query action—resolves a query built in the editor, 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. Pair it with a loop to process each match.
- On Demand from content—when an on-demand automation is registered for a content type, editors can run it directly from that content's edit page, without opening the flow editor. See Triggers.
Jira
Reacts to and acts on Jira issues.
- Trigger—the Jira trigger fires on issue and comment events for a project, optionally refined with JQL.
- Action—the Jira action runs one operation against a project: Create Issue, Get Issue, Update Issue, Assign Issue, Transition Issue, Add Comment, Search Issues, Delete Issue, Add Worklog, Link Issues, Add Watcher, and Remove Watcher.
GitHub
Reacts to and acts on a GitHub repository.
- Trigger—the GitHub trigger fires on repository webhook events such as pushes, pull requests, issues, releases, and workflow runs.
- Action—the GitHub action runs one operation against a repository, grouped by what it targets:
- Pull requests—Create, Get, Update, Merge, Submit Review, Add Reviewers.
- Issues—Create, Get, Update.
- Issues and pull requests—Add Comment, Modify Assignees, Modify Labels.
- Branches—Create, Get, List, Delete.
- Files and commits—Get File Contents, Create or Update File, Create Commit, Create Commit Status.
- Releases—Create Release.
- Workflows—Trigger Workflow.
Slack
Sends messages and collects approvals.
- Action—the Slack Message action posts a message to a user or channel. Slack is also where human-in-the-loop approvals can be presented and answered.
Composing the message
The Message field offers four ways to write it. Pick the one that matches how much control you need—every one of them accepts variables.
| Type | What it is | Reach for it when |
|---|---|---|
| Formatted | A rich-text editor: bold, italic, strikethrough, links, inline and block code, bulleted and numbered lists, and tables. | Almost always. It is the default, and what you type is what Slack shows. |
| Markdown | Standard markdown, rendered by Slack. Adds headings, task lists, and fenced code blocks with syntax highlighting. | The content is already markdown—most often an AI agent's output. |
| Blocks | An ordered list of Slack blocks configured one at a time: headers, sections, images, tables, charts, cards, carousels, buttons, and more. | You want structure a text editor cannot express, such as a chart or a two-column summary. |
| Raw Block Kit JSON | A Block Kit payload pasted verbatim. Accepts both shapes Slack's Block Kit Builder produces. | You need exact control, or a block type not listed under Blocks. |
A note on Formatted versus Markdown. Formatted treats your text as text: punctuation such as *, _, and ` arriving from a variable reaches Slack as those literal characters. Markdown treats the same punctuation as syntax. So if a variable might contain arbitrary prose, use Formatted; if it contains markdown you want rendered, use Markdown.
The Formatted editor deliberately offers only formatting Slack can render. Underline, superscript, and subscript are absent because Slack's message format has no equivalent for them—a message using them would lose that styling silently on delivery.
Link previews
Slack expands a preview card beneath any link it recognises. Turn on Hide Link Previews to suppress them for a message—useful when the message is mostly links and the previews would bury the text. Left off, Slack applies its usual behaviour.
Microsoft Teams
Sends messages to channels and collects approvals.
- Action—the Teams Message action posts a message to a channel. Teams is also where human-in-the-loop approvals can be presented and answered.
Recipient selection is picker-only: pick a team, then a channel within it. You choose display names, never raw IDs, and both lists come from the connection. When an administrator has curated a subset of allowed teams on the connection, the team list is that subset.
Composing the message
The Message field is a rich-text editor offering only the formatting an Adaptive Card can render: bold, italic, links, and bulleted and numbered lists. Underline, strikethrough, superscript, subscript, headings, tables, and inline code are absent because Teams shows their markdown as literal characters rather than as formatting.
Links come from the Elements dropdown rather than a toolbar button, and take an external URL only. A link to CMS content would not resolve for whoever reads the message in Teams.
Content pasted from another editor keeps its text and loses only the styling Teams cannot show.
Email
Sends email notifications.
- Action—the Email action sends a message to one or more recipients. It needs no connection; delivery is configured by an administrator. See Actions.
OpenAPI
Calls any service described by an OpenAPI specification.
- Action—the OpenAPI action calls a chosen operation from a spec you point it at, deriving its input fields from that operation. It needs no connection of its own. See Actions.