Wrike Make integrationAutomate Wrike with Make.
Can Make create, update and track Wrike tasks for you? Yes. The Wrike Make integration gives you 12 modules: 2 triggers, 7 actions and 3 searches. This guide is for Wrike users new to Make, and it walks you from the connection to a first working scenario.
Verified Trustpilot reviews · AI, automation & growth agency
What can the Wrike Make integration do for you?
The Wrike Make integration links your Wrike account to Make so tasks, folders and time records move without copy and paste. You build a scenario, the automation itself, out of modules: each module is one brick, like a trigger that watches Wrike or an action that creates a task.
Requests turn into tasks on their own. A form, an email parser or a support tool sits at the start of the scenario, and Create a Task drops each new request into Wrike. Nobody retypes the request, and nothing waits in an inbox.
Other tools hear about task changes. Watch Tasks picks up tasks that were created or modified, and the next module forwards them to a chat app or a reporting sheet. For a change that needs a reaction right away, Watch Events is the instant option.
Time tracked elsewhere lands in Wrike. When hours are recorded in another tool, Find Tasks locates the matching task and Create a Timelog writes the entry against it, so project reports stay complete.
What the app does not cover out of the box: the 12 modules focus on tasks, folders and timelogs. Anything else in the Wrike API goes through Make an API Call. The Make documentation for Wrike also warns that its own content is AI-generated and may contain mistakes, so check anything critical in Wrike itself. The same app often has an n8n node too; the n8n vs Make comparison helps you pick, the Make review covers the platform as a whole, and Make troubleshooting helps when a run fails.
How do you connect Wrike to Make?
- 01
Prepare your Wrike API client
You need an active Wrike account and an API client created in the Wrike Developer portal. In the App Console, open your application, enter the callback URI
https://www.integromat.com/oauth/cb/wrike2if asked, then copy the Client ID and the Client secret. - 02
Add a Wrike module in Make
Log in to Make, add any Wrike module to your scenario and click Create a connection. A connection is your Wrike account linked to Make once; every Wrike module in your scenarios then reuses it. The Connection name field is optional.
- 03
Enter your credentials
Paste the credentials you copied from Wrike, or follow the instructions on screen, and confirm. Make can now read your Wrike account, so the next module fields show real options from your workspace instead of empty boxes.
Your first scenario: turn incoming requests into Wrike tasks
GoalWhen a new request arrives in another app, Make creates a matching task in Wrike.
- 01
Create the scenario
Open the Scenarios page, create a new scenario and click the big +. Pick the app where requests come in, a form tool for example, and choose its trigger module.
- 02
Add Create a Task
Click the + on the right of that first module, search for Wrike and pick Create a Task. Click Create a connection if Wrike is not linked yet.
- 03
Fill the task from the request
Once the connection exists, Make lists what it can read in Wrike, so you choose from a list instead of typing IDs. Map the request details from the first module into the task fields.
- 04
Test with Run once
Click Run once, then send one test request. Each module shows the bundles it received, a bundle being one item passed along. Open Wrike and check that the task looks right.
- 05
Schedule it and switch it on
Set the schedule on the first module; a new scenario runs every 15 minutes by default. Then switch the scenario on, and new requests start becoming Wrike tasks without you.
Which Wrike triggers can start a scenario?
2 modules start a scenario when something happens in Wrike. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Wrike as soon as it happens.
Watch Events
Instant triggerIn Make“Triggers immediately when a new event is fired.”
Watch Events starts your scenario the moment Wrike reports a new event, so the follow-up runs without waiting for the next scheduled check. It is the only instant trigger among the Wrike modules.
Watch Tasks
Scheduled triggerIn Make“Triggers when a task is created or modified.”
Watch Tasks feeds your scenario the Wrike tasks that were created or modified, one bundle per task. That gives you a steady stream of task changes to copy, report on or pass to another tool.
What can Make do in Wrike?
Wrike gives you 10 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Create a Folder
ActionIn Make“Creates new folder.”
Create a Folder gives a new piece of work its own home in Wrike before any task lands there. The folder exists as soon as the module runs, ready for the next steps.
Create a Task
ActionIn Make“Creates new task.”
Create a Task writes a new task into Wrike from data that came in earlier in the scenario. Requests stop living in inboxes and show up where your team already plans its work.
Create a Timelog
ActionIn Make“Create timelog record for task.”
Create a Timelog adds a time record to a Wrike task, so hours spent show up in your project reports. It works on one task at a time, which means you need that task first.
Delete a Folder
ActionIn Make“Deletes a folder by its ID.”
Delete a Folder removes a Wrike folder you point to by its ID. Useful for tidying up structures that another step of your process has made obsolete.
Delete a Task
ActionIn Make“Deletes a task by ID.”
Delete a Task removes one Wrike task, identified by its ID. Paired with a search, it clears out tasks that should never have been created.
Make an API Call
ActionIn Make“Performs an arbitrary authorized API call.”
Make an API Call reaches any endpoint of the Wrike API with the connection you already set up. It is the way out when none of the 11 other modules does what you need.
Modify a Task
ActionIn Make“Updates a task.”
Modify a Task updates a Wrike task that already exists, so the task keeps pace with what happens in your other tools. No duplicate, just the same task brought up to date.
Find Tasks
SearchIn Make“Searches among all tasks in the current account.”
Find Tasks searches across all the tasks in your Wrike account and hands back whatever matches. This is how a scenario figures out which task an outside event is about.
Get Task(s)
SearchIn Make“Returns information about specific task(s).”
Get Task(s) returns the details of specific Wrike tasks you already point to. Handy when an earlier module gave you tasks and you want their full information in the scenario.
List Tasks from a Folder
SearchIn Make“Retrieves a list of tasks from a specified folder.”
List Tasks from a Folder brings back the tasks stored in one Wrike folder, one bundle each. You get a clean way to work through a single project instead of the whole account.
Need help automating Wrike with Make?
A person reads every message.
