.png?fit=max&auto=format&n=V5LGcGniNC1X_QJO&q=85&s=8c9ba3ce9a0d0045976180c9f669af26){kind=logo}
Actions
An action node is where the automation does something. Actions run after your trigger fires and any conditions pass. Each action node calls a connector to perform a specific operation — sending a message, creating a task, posting to an external service, or anything else the connector supports. Actions run in the order defined by the graph. Each action receives data from upstream nodes and produces its own output that downstream nodes can reference.Two types of action nodes
Collabase built-in
Native Collabase operations — create and update tasks, pages, and registry objects; send in-app notifications; trigger test runs. No connection setup required.
Connector actions
Actions from 40+ external connectors — Slack, GitHub, Jira, Stripe, Datadog, and more. Require a saved Connection with credentials.
Connections — credentials for connectors
Before using an external connector in an action node, you must create a Connection for it. A connection is a named, encrypted set of credentials that you configure once and reuse across all automations.1
Go to Automation → Connections
Open your Space, select Automation in the sidebar, then click Connections in the top navigation bar.
2
Click + New Connection
Click the + New Connection button. A dialog opens.
3
Select the connector
Choose the connector you want to connect (for example, Slack, GitHub, or Jira).
4
Enter your credentials
Fill in the required fields. Each connector lists what it needs — typically an API key, a token, or OAuth credentials. See the connector’s individual page for details.
5
Test and save
Click Test Connection to verify the credentials work, then click Save. The connection is now available in the action node picker inside any automation.
Credentials are encrypted at rest. They are never shown in execution logs or run history.
Adding an action node
1
Open the automation builder
Open your automation. Click the + button on any connection in the canvas, or drag a node from the node panel.
2
Choose Action
Select Action from the node type list.
3
Select a connector
Pick the connector from the list (for example, Slack, Jira, or Collabase built-in).
4
Select an operation
Pick the specific action the connector should perform (for example, Send Message or Create Issue).
5
Select a connection
For external connectors, select the saved connection to use. If no connection exists yet, click + New Connection to create one.
6
Fill in field values
Configure each input field. Use variable syntax to reference data from upstream nodes.
Field value syntax
All action input fields support variable references. Use these forms to pull data from upstream nodes:
Supports dot-notation for nested values and array indexing:
Action output
Every action node produces output fields that downstream nodes can reference using{stepOutputs.nodeId.fieldName}. The node’s ID is set in the node configuration panel — give it a short, descriptive name.
For example, if you name a Create Task node createTask, downstream nodes can reference:
{stepOutputs.createTask.id}— the ID of the created task{stepOutputs.createTask.taskKey}— the task key (e.g.PROJ-42){stepOutputs.createTask.url}— a direct link to the task
Retry policy
Action nodes can be configured to retry automatically if they fail. Set the retry policy in the node’s configuration panel.
Retries are counted in the execution log. If all retries fail, the node is marked as failed and the execution status becomes
FAILED or PARTIAL.
Connector actions reference
Each connector’s available actions are documented on its individual page.Communication
Slack, Teams, Discord, Email, Telegram…
Developer Tools
GitHub, GitLab, Jira, Sentry…
AI & Utilities
OpenAI, HTTP, Transform, Code…