Bring Wrike activity into Coherence
Start from a supported Wrike event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Task
Finishes with
Create or update a Coherence record

Wrike currently provides 3 triggers that can start a workflow and 9 actions a workflow can run. Use those building blocks to turn activity in one tool into an owned next step in the shared workspace.
New Task
Fires when a new task is created in Wrike (optionally within a folder).
New Folder
Fires when a new folder (or project) is created in Wrike.
New Subtask Created
Triggers when a subtask is created.
Create Task
Create a new task in Wrike
Update Task
Update fields of an existing task in Wrike
Create Folder
Create a new folder in Wrike
Create Project
Create a new project in Wrike
Add Comment
Add a comment or internal note to a task or folder
Upload Attachment
Upload a file and attach it to a task or folder
Find Task
Retrieve a task by its ID or lookup fields
Find Folder / Project
Retrieve folder / project metadata by ID or name
Custom API Call
Make a custom API call to a specific endpoint
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Wrike event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Task
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Wrike action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Create Task
Combine Wrike with another integration and Coherence records to turn activity in one tool into an owned next step in the shared workspace.
Starts with
New Task
Finishes with
Create Task, then preserve the outcome in Coherence
The exact authentication fields depend on Wrike. The workflow structure stays straightforward:
Authorize the Wrike account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Wrike or provide a complementary trigger or action.
Wrike currently provides 3 triggers that can start a workflow and 9 actions a workflow can run. Use those building blocks to turn activity in one tool into an owned next step in the shared workspace.
Wrike currently lists 3 triggers and 9 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Wrike triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.