Skip to main content

​
Actions

An action node is where the automation does something. Actions run in sequence after your trigger fires and any conditions pass. Each action receives the output of the node before it, and produces its own output that subsequent nodes can use via {{previous.fieldName}}.

​
Two types of actions

Collabase built-in

Native Collabase operations — create and update tasks, pages, and registry objects; run test cases; send in-app notifications. No connection setup required.

Connector actions

Actions from your 38 external connectors — Slack, GitHub, Jira, Stripe, Datadog, and more. Require a saved Connection with credentials.

​
Variable references

All action input fields support {{variable}} syntax to reference data from upstream nodes: 
{{testCaseTitle}}           ← from the trigger
{{previous.id}}             ← from the immediately preceding node
{{stepId.fieldName}}        ← from a specific named node
{{payload.environment}}     ← from a webhook payload
Chain outputs: the result of one action feeds into the next. If a Slack Send Message action returns {{previous.ts}} (the message timestamp), a subsequent Update Message action can reference it.

​
Connector actions reference

Each connector’s available actions are documented on its individual page.

Communication

Slack, Teams, Email, Telegram…

Developer Tools

GitHub, GitLab, Jira, Sentry…

AI & Utilities

OpenAI, HTTP, Transform, Code…
→ View all 38 connectors