Resources · Zapier integration

Wrike Zapier integrationAutomate Wrike with Zapier.

The Wrike Zapier integration offers 2 triggers and 6 actions. Zapier can spot new folders and new tasks in a folder you pick, then create tasks, projects, comments and time entries for you. Here is what each one does, what it costs and where it trips.

See the 8 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Wrike Zapier integration does for your projects

Connecting Wrike to Zapier lets new work in Wrike start things elsewhere, and lets other apps create work in Wrike, without code. Zapier watches one folder you choose for new subfolders or new tasks, and it can add folders, projects, tasks, comments and logged hours.

Three results come up most once the connection is live.

New client requests become Wrike tasks. A form answer, a deal won in your CRM or a support ticket triggers Create Task, so nobody retypes the request. A marketing team gets every brief in the same place.

Each new project gets its scaffolding. When New Folder spots a new subfolder under your clients folder, the Zap can follow with Create Comment to post the kick-off note there, or Create Project to open the delivery project next to it.

Hours land where they belong. Create Time Entry logs hours into a folder from another tool, which keeps billable time in Wrike even when people track it elsewhere.

What Zapier does not do here: both Wrike triggers are polling ones, so nothing starts instantly. There is no trigger for an updated or completed task, and no search step to find an existing task before writing. Nothing is deleted or edited either; every action creates something new. For a reading of the same app on another platform, see the Wrike Make integration.

Vocabulary

Zapier words you will meet on this page

Seven terms in plain English, so the notes below read without a dictionary.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event in an app that starts the Zap. On Wrike, that is a new folder or a new task in the folder you choose.
Action
What the Zap does once started: the step that creates a task, a folder, a comment or a time entry for you.
Task
In Zapier's sense, the unit it bills: one action completed successfully. Not to be confused with a Wrike task.
Polling vs instant
Polling: Zapier checks the app on a timer. Instant: the app reports the event itself. Both Wrike triggers poll.
Filter
A step that lets the Zap go on only when what arrived meets your condition, and stops it quietly otherwise.
Connection
Your Wrike account linked to Zapier once, then reused by every Wrike step in every Zap you build.
Cost

What a Wrike Zap really costs

Zapier bills tasks: each Wrike action that succeeds is one. The trigger, and every check Zapier makes on your folder, cost nothing.

  • Trigger checksFree, however often
  • Each successful action1 task
  • Failed actionNot counted
  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo, works on the free plan

Wrike is not a premium app, so it runs on the free plan: 100 tasks a month, two-step Zaps (one trigger, one action), and a check of your folder every 15 minutes. A second action, a filter or a search makes the Zap multi-step, which needs a paid plan. An action that fails is not counted. Paid plans also check more often, as the grid shows, which matters here because both Wrike triggers poll. Start simple, then upgrade.

Connect

Connect Wrike to Zapier in three steps

  1. 01

    Open the connection dialog

    From your Zapier account, open the Apps page and click + Add connection. Type Wrike in the search box of the dialog and pick it from the results. It is listed under its own name.

  2. 02

    Sign in to Wrike

    Click Add connection. Wrike opens in a new tab: sign in with an account that can see the folders your Zaps will watch, and write in the ones they will fill.

  3. 03

    Grant access

    Allow Zapier to work with your Wrike account. The connection is saved once, and every Wrike step in every Zap can reuse it from then on. No extra setup is needed per Zap.

First Zap

Your first Wrike Zap: a kick-off note on every new client folder

GoalEach time someone adds a subfolder under your Clients folder in Wrike, the Zap posts a kick-off comment in it so the team knows the account is open.

  1. 01

    Build: pick the trigger

    In a new Zap, choose Wrike and New Folder. Set Folder to your Clients folder: the trigger watches the subfolders created inside it.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent subfolders, so you can pick a real one and map from it in the next step.

  3. 03

    Add the Wrike action

    Add Create Comment. Map the new folder into Folder, leave the task fields empty so the note goes to the folder's comment stream, and write the text.

  4. 04

    Test the action

    Run the test and open the folder in Wrike. The comment should be there. One run of this Zap costs one task. Check the text reads well before going on.

  5. 05

    Publish

    Click Publish. From now on, Zapier checks the folder on your plan's interval. Subfolders created before publishing are left alone.

Triggers

The 2 Wrike triggers

2 events start a Zap when something happens in Wrike. Zapier checks for them at the interval your plan allows.

1

New Folder

Polling trigger

In Zapier“Triggered when a new folder is created.”

Starts your Zap when a subfolder appears inside the folder you point it at. Think of it as a doorbell on one shelf of your Wrike workspace: anything added elsewhere goes unnoticed.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
an agency that opens one subfolder per client and wants each new one to set off a welcome note, a project or a request in another app.
Watch out
the Folder setting is mandatory, so pick the parent where new folders really get created, not the space above it.
2

New Task

Polling trigger

In Zapier“Triggered when a new task is created.”

Fires whenever a task is added to the folder you choose. You also decide whether tasks created in its subfolders count, through the Track Subfolders setting, which Zapier asks you to fill in.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a content team that wants every new article task in its editorial folder copied into a chat channel or a planning sheet.
Watch out
if the same Zap uses Create Task in that folder, every task it creates sets the trigger off again. Point the action at another folder.
Actions

The 6 Wrike actions, grouped by what they do

Wrike gives you 6 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Comment

Action

In Zapier“Create a new comment.”

Posts a comment with the Comment Text you set, in the Folder you choose. If you leave both task fields empty, it lands in the folder's own comment stream instead of on a task.

When to use it
dropping a status note on a project when something happens in another app, such as a payment received.
Watch out
to comment on a specific task, fill one of the task fields, or the note stays at folder level.
2

Create Folder

Action

In Zapier“Create a new folder.”

Makes a new folder under a Parent Folder you pick, with the Title you map. Both settings are required.

When to use it
opening a client folder automatically when a contract is signed in another tool.
Watch out
a New Folder trigger on that same parent will see the folder this action creates.
3

Create Project

Action

In Zapier“Creates a new project.”

Opens a Wrike project under a Parent Folder, with a Title. An optional switch, With Invitations?, decides whether invitations go to the owners and the people the project is shared with.

When to use it
starting a delivery project the moment a deal moves to won.
Watch out
decide on that switch before you publish, so invitations only go out when you mean them to.
4

Create Task

Action

In Zapier“Create a new task.”

Adds a new task in Wrike from data that arrives in the Zap, in the folder you point it at.

When to use it
turning each form submission, won deal or support ticket into a task so it gets assigned instead of forgotten in an inbox.
Watch out
do not create tasks in the folder a New Task trigger is watching, or the Zap feeds itself.
5

Create Time Entry

Action

In Zapier“Create a new time entry.”

Logs hours into a Folder. The Hours field is required and accepts fractions, so half an hour is fine.

When to use it
a consultancy whose people track time in another tool but bill from Wrike.
Watch out
the value goes in as hours, so convert minutes from the source app before mapping them.
6

API Request (Beta)

Action

In Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”

An advanced step that sends a raw request to Wrike using the connection you already set up. You pick the HTTP Method and the URL, and the URL must belong to Wrike's own domains.

When to use it
reaching something the five other actions do not cover, if someone on the team is comfortable with Wrike's API.
Watch out
Stop on error is required; set it to Yes so a failed call halts the Zap.
When it breaks

When a Wrike Zap breaks

Zapier attaches no help article to Wrike, so the traps below are Zapier's general ones, applied to how Wrike's folders and tasks behave.

None of these are bugs. They follow from two facts: both triggers poll a folder, and every action creates something. When a Zap still misbehaves after these checks, Zapier troubleshooting is the next stop.

  • A Zap that creates what it watches

    New Task plus Create Task in the same folder sets itself off again and again, and burns through your task count fast. Write into another folder.

  • Old folders and tasks are skipped

    A Zap only reacts to what is created after it is switched on. Tasks already in the folder are not picked up; moving that backlog is a separate job.

  • A big import can be held back

    If a template or a migration drops a huge batch of tasks at once, Zapier's flood protection can hold them back instead of running the Zap for each.

  • The same task never fires twice

    Zapier keeps track of what it has already seen on a polling trigger, so one new task starts the Zap once. To react to a change, the Zap needs a new item.
Need help

Need help automating Wrike with Zapier?

A person reads every message.

FAQ

Wrike Zapier integration: frequent questions

01Is the Wrike Zapier integration free?
Yes, it works on Zapier's free plan, since Wrike is not a premium app. That plan gives you 100 tasks a month and two-step Zaps, one trigger and one action, with Zapier checking your Wrike folder every 15 minutes. Add a filter, a search or a second action and the Zap becomes multi-step, which needs a paid plan. A simple New Folder then Create Comment Zap fits on the free plan.
02How many tasks does a Wrike Zap use?
One Zapier task per Wrike action that succeeds. The trigger never costs anything, and neither do the checks Zapier makes on your folder, however often they happen. So a Zap that creates one Wrike task per form answer uses one Zapier task per answer, and a Zap with two actions uses two per run. An action that fails is not counted. Keep in mind that a Zapier task and a Wrike task are two different things.
03Is Wrike on Zapier real time?
No. Both Wrike triggers, New Folder and New Task, are polling triggers: Zapier goes and checks your folder on a timer. The interval depends on your plan: 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. On paid plans you can also run a check by hand from the editor. Actions that write into Wrike run as soon as the Zap reaches them, whatever triggered it. Plan for that delay.
04What does it take to connect Wrike to Zapier?
A Wrike account and a Zapier account. You add the connection from the Apps page with + Add connection, sign in to Wrike in the tab that opens and grant access. The account you use matters: triggers and most actions ask for a Folder, and that account needs access to the folders in question. Sign in with a user who has access to the spaces your Zaps will touch. That avoids empty lists later.
05Why does a Wrike Zap keep running on its own?
Most likely because it writes into the folder its own trigger is watching. A New Task trigger and a Create Task action on the same folder form a loop: each task the Zap creates is a new task, which starts the Zap again. The same goes for New Folder with Create Folder under the same parent. Turn the Zap off, then point the action at a different folder or add a filter that lets only outside tasks through.
06What if the Wrike operation you need is not on Zapier?
Then the integration does not offer it out of the box. Zapier's Wrike app has two triggers and six actions: no trigger on updated or completed tasks, no search, no edit or delete. The sixth action, API Request (Beta), lets someone comfortable with Wrike's API send a raw request through your existing connection, limited to Wrike's own domains. Otherwise, check the same app on Make or n8n. Start from that list.
07Zapier, Make or n8n for Wrike?
Compare them on criteria, not on a ranking. Coverage: on Zapier, Wrike offers two polling triggers, five create actions and API Request (Beta), so check whether you need updates or searches. Speed: polling means a delay set by your plan, from 15 minutes on Free down to 1. Cost: Zapier counts one task per successful action, which makes the bill easy to forecast for a project team. Weigh the three together. None of them wins on every point.
Same platform

Other docs you might need on this stack.

Browse all integrations