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

[ Productivity ]

Wrike integration for your workflows.

Connect Wrike to Collabase once and use 9 actions and 3 triggers in your workflows. No code needed, hosted in Switzerland.

Sign-inOAuth 2.0
CategoryProductivity
UpdatedSeptember 2026
LicenceOpen source (MIT)
Back to the directory

Wrike in Collabase

Connect Wrike to Collabase once and use 9 actions and 3 triggers in your workflows. No code needed, hosted in Switzerland.

How to connect it

  1. Open the integrations in the workspace settings.
  2. Choose Wrike and connect your account.
  3. Add a trigger or an action to the workflow.
  • Go to Wrike (https://www.wrike.com/)
  • Sign in to your account or create one
  • Go to Apps & Integrations (https://www.wrike.com/apps/)
  • Click "Create new app" or use an existing one
  • For local development, add http://localhost:4200/redirect to the allowed redirect URIs
  • Copy the Client ID and Client Secret

[ Productivity ]

Related integrations

All integrations

Tools that often share a workflow.

Questions about Wrike

What can I automate with Wrike in Collabase?

Wrike brings 9 actions and 3 triggers, for example Create Task, Update Task, Create Folder, Create Project and 5 more. You combine them in a workflow without code and mix them with every other integration.

How do I connect Wrike to Collabase?

You open the integrations in the workspace settings, choose Wrike and connect your account once, using OAuth 2.0. After that all triggers and actions are available in the workflow.

Can Wrike start a workflow?

Yes. Wrike provides 3 triggers, for example New Task, New Folder and New Subtask Created. The workflow runs as soon as the event happens.

Does the Wrike 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.