Build my stack
All Wrike connections
Discover what apps integrate directly with Wrike or sync parameters using webhook pipelines.
No connections documented for Wrike yet
We have not yet verified any integrations for Wrike. Rather than fill this page with claims we have not tested, we are leaving it short and telling you so plainly.
What each connection type actually means
Native integration
A direct, vendor-built connection between the two products. It is the cheapest to run and the most likely to be maintained when something changes.
API
You call one product's API from the other, usually through a small script or a workflow step. Flexible, and entirely your responsibility to keep working.
Webhook
One product posts to a URL when something changes. Cheap and event-driven, but you still need something on the receiving end to store the payload.
Via Zapier
Zapier holds the connection for you. No maintenance, and you pay per task in both money and in one more service that can fail.
Via n8n
The same idea as Zapier on infrastructure you control. Cheaper at volume, and you fix it yourself when a vendor changes an API.
Integration coverage across the category
Integration coverage matters more than most buyers expect, because it decides how much glue code your team maintains. We have verified integrations for 2 tools in project management, and the spread between them is wide.
Notion leads on coverage with 4 verified integrations, including 2 vendor-maintained connections.
1 tool here has one or two verified connection: ClickUp. If you need deep integrations, treat that as a risk and check the vendor's own directory before you commit.
Coverage counts here are what we have personally verified, not what the vendors claim. A vendor with forty integrations on their marketing page and two that actually work is worse off than one with four that all work, and that is the distinction this table is trying to make.
Why you would want Wrike at all
Integrations are the reason a tool is disqualified, but they are rarely the reason one is chosen. Wrike is a powerful project management platform built for teams that have outgrown simpler tools. It suits mid-size to enterprise teams that need flexible project management with advanced resource planning and approval workflows, and that is the part worth reading before you look at any connection list.
It costs $9.80 per month, with a free tier as well. Integration work has a cost too, and if you are going to build automations yourself through n8n, that cost belongs in the same column as the subscription.
The price has held at $9.80 a month across every point we have recorded, so nothing in the pricing argues for waiting.
The drawbacks we found in testing were steep learning curve: 2 to 4 weeks for full adoption, ui feels dense and dated compared to linear or asana, and mobile app lacks feature parity with desktop. Integrations do not fix those, and it is worth knowing what they are before you wire this into your workflow.
If you need wider coverage
Integration questions
How many integrations does Wrike have?
We have personally verified 0 integrations for Wrike, which puts it at 0 in our coverage table for this category. None of them are vendor-maintained, which means you own the maintenance. We publish the number we have verified rather than the number the vendor markets.
Does Wrike have a native integration or do I need Zapier?
Not for anything we have verified. Every connection we have for Wrike runs through an automation platform rather than a native link, so there is no vendor-maintained path in our dataset.
Is Zapier or n8n better for connecting Wrike?
Neither, on our current data. We have not verified an automation-platform connection for Wrike, so we are not going to recommend a tool for a workflow we have not seen run.
What is the most integrated project management tool you track?
Notion, with 4 verified integrations in our dataset, 2 of which are maintained by the vendor. Wrike has 0, so if deep integrations are a hard requirement rather than a nice to have, Notion is the safer choice on this evidence.
How do you test whether an integration actually works?
We connect the two tools with real data in both directions, trigger a change on one side, and confirm it lands on the other. Then we change something a second time, because an integration that works once is the normal failure mode. Anything we could not get working we list as broken rather than quietly dropping, and anything maintained by a third party we mark community.
Can I request an integration you have not tested?
Yes, and we would rather you asked than bought blind. Tell us which tool connects to which, and if it matters to real buyers we will test it and add the result with the steps we used. The gaps in this dataset are ours, not the vendor's, and we would rather close them than pretend they are not there.
Integration counts on this page are the connections we have personally verified, not the vendor's own marketing count. That is a smaller number, and it is the one that matters. We test a connection twice, because one that works once is the normal failure mode.