Productivity · Integration
Wrike
Add Wrike to your product for your customers, and give your AI agents governed access to it.
Wrike organises work as a tree that is really a graph. A task lives in a folder, but it can live in several folders at once, projects are folders with dates and an owner, and spaces sit above all of it, which means the same task legitimately appears in two places and an integration that assumes one parent gets it wrong. On top of that sit custom fields and custom item types, so what a request or a bug looks like differs per account. An embedded Wrike integration creates and updates tasks, sets assignees, dates and statuses from your own workflow, reads folder and project structure, logs time, and receives webhooks when something changes so your product is not polling for it. fastn keeps each customer's tokens per tenant and follows the API as it moves.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Wrike account so work your product creates appears in the space their team already lives in.
Create a task in the folder or project a customer nominates, with the custom fields that account requires filled in.
Map your own workflow stages to that customer's statuses, since two Wrike accounts rarely name them alike.
Receive webhooks on task and folder changes so your product reacts when work moves rather than on a schedule.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent reports what is assigned to a person this week across the folders it may read.
An agent creates or reassigns a task inside scoped permissions, with the change attributed.
An agent explains why a project is behind by reading its task dates and dependencies.
Example prompt
What is overdue in this Wrike space right now, and who is each item assigned to?
Set up Wrike in 4 steps
- 01Enable the Wrike connector in your fastn dashboard.
- 02Have each customer authorise their own account so tasks are created under their credentials.
- 03Map that account's spaces, custom fields and statuses, and decide how your product handles a task that sits in several folders.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Wrike integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Wrike integration without building it. Your customers connect their own Wrike account inside your product and work their work items, assignees and due dates there, with no per-customer code on your side.
- Handle the part that actually costs time: every team configures its own fields, statuses and workflow stages. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Wrike update is not your on-call problem.
- One integration serves your product and your agents. The same governed Wrike connection powers in-product features and gives AI agents scoped, audited access, so you keep work items in step with what happens in your product without wiring it twice.
Used by these teams
Compare with
Asana
ClickUp
SmartsheetOften used alongside
Tools the same teams tend to run next to Wrike, across other categories.
Notion
Box
Docusign
AWS Simple Storage ServiceWrike integration FAQ
How do I add a Wrike integration to my product?
Enable the Wrike connector in your fastn dashboard, then let each customer authenticate their own Wrike account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Wrike client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Wrike account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Wrike account and only ever sees their own work items, assignees and due dates. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Wrike integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent reports what is assigned to a person this week across the folders it may read.
Who maintains the Wrike integration?
fastn does. When Wrike changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can my product create and update work in Wrike automatically?
Yes. Items can be created, updated, assigned and transitioned from your product, and changes made in Wrike can trigger your workflows in return.
Does it adapt to each team's own Wrike setup?
Yes. However a team has configured Wrike, whether that is custom fields, statuses and workflow stages or its own calendars and working hours, those are mapped per customer, so an unusual setup works without custom code from you.
What can I build with the Wrike integration?
A common starting point: let each customer connect their own Wrike account so work your product creates appears in the space their team already lives in. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Wrike integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Wrike does not change your per-connector cost. You can start free with 3 connected accounts.
Add Wrike to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.