Actions

An action is a step that does work—calling a service, transforming data, operating on content, or notifying someone. Add one by clicking + on an edge and selecting Action, then choosing a type from the panel.

The panel groups actions into General Actions, Notification Actions, AI Actions, and Integration Actions. This page covers all four groups, in that order.

Most action fields accept variables, so you can feed in values from the trigger and earlier steps. For full field-level detail, see the Reference.

General actions

Action	What it does
HTTP Request	Sends an HTTP request to any URL, with a method, query parameters, headers, body, and optional authentication. You control how the response is captured—status only, headers, the body inline, or streamed to storage for large responses. The action can be set to fail on a non-success status so the flow follows its error path. An optional resilience policy adds retry with backoff, a per-attempt timeout, and circuit breaking, so a step can ride out a flaky endpoint on its own.
Script	Runs a script in a sandbox. The script can read the incoming payload and your mapped input, and return a value. Optionally declare the output's shape so later steps can reference its fields. The sandbox has no file system, network, or host access, and bounds how long a script runs and how much memory it uses—see Script action.
Sleep	Pauses the flow for a set duration, then continues. The run waits without consuming resources while it sleeps.
Automation	Runs another automation through its on-demand trigger. You can fire it and continue immediately, or wait for it to finish and read its outcome—a failed outcome can follow this node's error path.
OpenAPI	Calls an operation from any OpenAPI specification. Point it at a spec URL and pick an operation; the action builds its input fields from that operation's parameters and request body.
Log	Writes a message to the run's execution log, then continues unchanged. Mix literal text with variables to record what a value holds at that point in the flow—a lightweight trace that doesn't need a Script step.
Stop with Error	Deliberately fails the run when the flow reaches it. Place it on a path that should never be taken—the false branch of a condition guarding an expected value—so an unexpected outcome becomes a visible failure instead of a silent success.

Notification actions

Action	What it does
Email	Sends an email to one or more recipients, with a subject and a rich-text body that can include variables. Recipients who have opted out are skipped, and each message includes an unsubscribe link. The result reports which addresses were sent, failed, or skipped. Email delivery is configured by an administrator.
Slack Message	Posts a message to a Slack user or channel through a Slack connection. The rich-text message is converted to Slack formatting, and the result includes the channel and message timestamp.

AI actions

Action	What it does
AI Agent	Runs an AI agent as a step, drawing tools from one or more connected MCP servers. You write the task as a prompt, and the agent can pause for a person to answer a question before continuing.
Remote AI Agent	Hands the task to a connected Brightspot CMS, whose own AI agent does the work with that CMS's tools. Use it when the task belongs entirely to one CMS.
AWS AgentCore	Invokes a hosted AWS Bedrock AgentCore agent, chosen from your AWS environment's catalog, with a prompt or JSON input.

All three pause for human-in-the-loop input when you enable it on the step. See AI and agents for how agent steps work.

Integration actions

Integration actions operate on an external system through a connection. Most are a single action with a set of operations—you pick the connection and target once, then choose what to do; switching operations keeps your connection and target. Content Query is the exception: instead of an operation, you choose the source its content list comes from.

Action	Operates on
Content	Content in a connected Brightspot CMS—fetch, publish, save, archive, delete, restore, transition a workflow, post a comment, or complete a work stream item.
Content Query	A query or a saved work stream in a connected Brightspot CMS, resolved to a list of content. Wire it into a loop to run the flow across every match instead of a single event.
Jira	Issues in a Jira project—create, update, assign, transition, comment, search, and more.
GitHub	A GitHub repository—pull requests, issues, branches, files and commits, releases, and workflow runs.

See Integrations for the full operation list per system.

Output and errors

Each action exposes an output that later steps can reference through the variable picker—for example, an HTTP response's status and json, or an email's sent and failed lists. When an action fails and you have enabled its error path, the flow follows that path instead of stopping; otherwise the run fails. See Building automations for error handling and Monitoring and history for reviewing failures.