Developer Platform: MCP server availableDeveloper Platform: MCP server available, App SDK from Q4 2026

Integrations

1000+ integrations. Your tools in one workflow.

Every integration brings triggers and actions. You connect them in a workflow without a line of code and run everything in Switzerland.

1000+Integrations
7019Actions
1653Triggers
16Categories

Popular

What teams connect first.

Chat, tickets, spreadsheets, CRM and AI: the integrations that appear in most workflows.

Directory

All integrations. Search, filter, open.

Search by name or start from a category. Each integration lists its triggers, actions and fields.

776 integrations

All integrations from A to Z

The complete directory as a list.

Build

Missing an integration? Build it yourself.

With the Plug SDK you write your own plugs for automation: triggers and actions for any system with an interface.

AI agents already work with Collabase through the MCP server. From Q4 2026 you write your own apps with webhooks, events and automation using the App SDK.

Questions about integrations

How many integrations does Collabase have?

The directory lists over 1000 integrations, from chat and tickets to CRM, accounting and AI. Each one brings triggers and actions for workflows. New integrations and changes appear in the directory continuously.

Do integrations cost extra?

No. All integrations are included in every licence, in the Isolated Cloud and in Self-Hosted operation. There is no module price.

How do I connect an integration to Collabase?

You open the integrations in the workspace settings, choose the tool and connect your account once. After that all triggers and actions are available in the workflow. The sign-in method is listed on each integration page.

What if my tool is missing?

With the Plug SDK you build your own integration for any system with an interface. Alternatively you call the interface directly through the HTTP integration.

Test it against your own content. A proof of concept is ready within days.

We set up an instance with your content and you test it against real workflows. In a first conversation we clarify scope, operating model and timing.