Automation

How it works
Every automation is built from nodes connected in a visual builder.Triggers
A trigger starts the automation — a Collabase event, a schedule, an incoming webhook, an external service event, or a manual run.
Conditions
A condition evaluates data from the trigger or a previous action and decides whether to continue. If it fails, the branch stops.
Actions
An action does something — creates a page, sends a Slack message, creates a Jira issue, calls an API, runs AI, or updates a registry object.
Execution model
When a trigger fires, the engine runs these steps in order:- Trigger fires — the event passes its output fields downstream
- Conditions evaluate — each condition either passes (continue) or fails (branch stops)
- Actions execute — each action runs, receives the previous output, and produces its own
- Execution is logged — every run appears in the Runs tab with per-step output
38 external connectors
Collabase ships with 38 pre-built connectors covering:Slack, Teams, Discord
GitHub, GitLab, Jira
HubSpot, Pipedrive, Stripe
Sentry, Datadog, PagerDuty
Google Drive, Sheets
Bexio, Abacus, Personio
OpenAI, Local AI
HTTP, Transform, Code
Connections
Before using a connector, create a Connection — a named, encrypted credential set. Go to Automation → Connections → + New Connection. Connections can be private, shared with a Space, or shared globally.Variables
Reference data from any upstream node with{{variable}} syntax:
Rate limits and quotas
| Limit | Default |
|---|---|
| Max executions per automation / minute | 60 |
| Max active automations per Space | 100 |
| Max action nodes per automation | 50 |
| Max execution duration | 5 minutes |

