What is the Plug SDK?
The Plug SDK is the toolkit you use to write your own plugs for Collabase automation. A plug connects Collabase to another system. It brings triggers and actions to the automation builder without changing the core. You describe the inputs as a schema, and the builder generates the form from it. The SDK is typed, open source under the MIT license and is coming in Q4 2026.
What a plug can do. The places where a plug takes part in automation.
Triggers
A plug starts an automation when something happens in another system, by webhook or at fixed intervals.
Actions
Steps that read data, write data or kick something off, with typed inputs and outputs.
Connections
API keys or OAuth, stored once by the admin. A plug only gets the connection of the running step.
Input forms
You describe fields, dropdowns and dependent fields in code. The builder renders them with Collabase components.
Resuming
If an automation waits or restarts, it continues at the last step. Steps never run twice.
Tests in the builder
A plug can be tested in the builder with real data before the automation goes live.
Built-in Collabase plugs. You do not have to start from zero.
Collabase ships plugs for its own modules, plus the usual building blocks for logic, data and schedules: branches, loops, webhooks, HTTP calls, tables and more. Your own plugs combine with them in the same flow.
Secure because isolated. A plug runs in isolation, and admins decide what gets installed.
[ 01 ]Its own sandbox
Third-party plugs run in a separate service, in an isolated process with memory, time and process limits.
[ 02 ]No access to the internal network
The sandbox reaches neither the database nor internal services. Outbound, only internet addresses are open, private address ranges are blocked.
[ 03 ]Minimal permissions
A plug receives a token for exactly one workspace and the connection of the current step. It never sees application secrets or other connections.
[ 04 ]Control for admins
Admins upload plugs or install them from the catalog, and check the licenses of the dependencies first. Plugs with a license that is not allowed are rejected.
[ 05 ]Data stays in the instance
Connections, runs and logs stay in your instance, backups included.
One command to a running plug. The CLI scaffolds the plug, builds it and packages it for your admin.
No catalog needed: the admin uploads the package to your instance.
The SDK is typed. Mistakes show up while you write.
# creates a working plug scaffold
$ npm create collabase-plug
# builds the plug
$ npm run build
# builds the package an admin uploads
$ npm run packageOpen source on GitHub. The Plug SDK, the CLI and the example plugs are MIT licensed. The built-in plugs and the engine are part of the product.
Repositories
- Collabase/plug-sdk
Framework, CLI and create-collabase-plug
- Collabase/plug-examples
Example plugs and template
npm packages
Coming Q4 2026- @getcollabase/plug-sdk
Triggers, actions, connections and input forms
- @getcollabase/plug-cli
build and package
- create-collabase-plug
Scaffold for a new plug
Not published yet. The packages ship from Q4 2026.
Questions about the Plug SDK
What is the Plug SDK?
The toolkit you use to write your own plugs for Collabase automation. A plug brings triggers and actions for another system to the automation builder.
When is the Plug SDK available?
From Q4 2026. The built-in plugs are already part of Collabase.
Which language do I write a plug in?
TypeScript. Inputs and outputs are typed.
How does a plug get into an instance?
The admin uploads the package or installs the plug from the catalog. The licenses of the dependencies are checked first.
Can a plug reach my database or internal services?
No. Third-party plugs run in a sandbox with no access to the internal network and only see the connection of their step.
Which license does the Plug SDK use?
The MIT license, as open source on GitHub. This covers the SDK, the CLI and the example plugs, not the built-in plugs or the engine.
Do I need a plug or an app?
A plug, if Collabase should talk to another system or be started by it. An app, if Collabase should get an interface or data of its own.
The other building blocks. They fit together, so your app looks and behaves like Collabase.
MCP server
AI agents work with your Collabase data through OAuth.
App SDK
Your own apps in TypeScript and React, running inside Collabase.
CollaKit
The design system with foundations, components and tokens.
AgentKit
Rules, skills and MCP access so agents build Collabase apps the right way.