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

Productivity

Linear integration for your workflows.

Connect Linear to Collabase once and use 13 actions and 8 triggers in your workflows. No code needed, hosted in Switzerland.

Sign-inAn API key
CategoryProductivity
UpdatedNovember 2026
LicenceOpen source (MIT)
Back to the directory

Linear in Collabase

Connect Linear to Collabase once and use 13 actions and 8 triggers in your workflows. No code needed, hosted in Switzerland.

About the service

Issue tracking for modern software teams

How to connect it

  1. Open the integrations in the workspace settings.
  2. Choose Linear and connect your account.
  3. Add a trigger or an action to the workflow.
  • In Linear, open Settings from the workspace menu at the top left.
  • Go to Security & access.
  • Under Personal API keys, enter a label and click Create key.
  • Copy the key (it starts with linapi) and paste it here.

Productivity

Related integrations

All integrations

Tools that often share a workflow.

Questions about Linear

What can I automate with Linear in Collabase?

Linear brings 13 actions and 8 triggers, for example Create Issue, Update Issue, Create Project, Update Project and 9 more. You combine them in a workflow without code and mix them with every other integration.

How do I connect Linear to Collabase?

You open the integrations in the workspace settings, choose Linear and connect your account once, using an API key. After that all triggers and actions are available in the workflow.

Can Linear start a workflow?

Yes. Linear provides 8 triggers, for example New Comment, New Issue, Updated Issue and 5 more. The workflow runs as soon as the event happens.

Does the Linear integration cost extra?

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

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.