Skip to main content
A plug connects Automation to a system that the catalog does not cover: your ERP, an internal service, a supplier’s API. It adds triggers, which start flows, and actions, which flows run as steps. Developers write plugs in TypeScript with the plug framework and upload them with the command line tool.
The Plug SDK, with its npm packages and the command line tool, is published from Q4 2026. See Plug SDK.

What a plug is made of

How a plug runs

A plug that Collabase did not write runs in the sandbox service, never in the application:
  • Each call runs in a locked-down process with its own memory and time limits. A process that failed is discarded.
  • The process has no route to your database or other internal services. It can reach the internet, and an address filter blocks private ranges.
  • The process gets one token for one workspace and the connection of the step that is running. It never sees application secrets or the connections of another workspace.
  • A step may run for up to 10 minutes.

The path to a running plug

1

Create the plug

collabase-plug init creates a folder with a manifest and a sample action. See Get started.
2

Write actions and triggers

Describe the inputs and write the code that calls the other system.
3

Build and check

collabase-plug build bundles the plug into one file and checks the licence of everything in it.
4

Upload

collabase-plug publish uploads the package to your instance. The instance checks it again and installs it. See Publish and versions.
5

Use it in a flow

The plug appears in the step list, marked as an own plug. Test an action, then build flows with it.

Plugs from the catalog

You may not need to build anything. The catalog lists hundreds of core and community plugs that an administrator can install. See Plugs and the plug reference.
Last modified on October 26, 2026