Connectors
Connectors extend the automation engine beyond Collabase-native actions. Each connector handles authentication, exposes typed actions, and optionally listens for incoming events from the external service. Collabase ships with 40+ pre-built connectors organized into categories below.Setting up a connection
Before using any connector in an automation, you save your credentials once as a Connection. The connection is encrypted and reused across all automations — you never enter credentials directly inside a node.1
Go to Automation → Connections
Open your Space and select Automation in the sidebar. 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 Bexio.
4
Enter your credentials
Fill in the required fields. Each connector lists exactly what it needs. See the connector’s individual page for where to find the credentials in the external service.
5
Test the connection
Click Test Connection. Collabase verifies the credentials against the external service and shows a success or error message.
6
Save
Give the connection a descriptive name (for example,
Slack — Engineering Workspace or Bexio Production) and click Save. The connection is now available in every automation’s action node picker.Credentials are encrypted at rest using AES-256 and are never shown in execution logs or run history. To update credentials, open the connection and edit the relevant fields.
Communication
Calendar
Storage & Data
CRM & Finance
Developer Tools
Project Management
Swiss ERP & HR
AI & Utilities
Individual connector pages
Each connector has its own documentation page with:- Authentication requirements and where to find credentials
- All available trigger events (for connectors that support them)
- All available actions with input and output fields
- Tips and common use cases
The HTTP connector lets you call any external service that is not covered by a dedicated connector. Use it to integrate with internal tools, custom APIs, or newer services not yet in the connector library. See the HTTP connector page for details on authentication, headers, and response handling.
.png?fit=max&auto=format&n=V5LGcGniNC1X_QJO&q=85&s=8c9ba3ce9a0d0045976180c9f669af26)
