

How to Send Wrike Task Updates to Slack with Zapier
Automatically posts a Slack message to a project channel whenever a Wrike task changes status, is completed, or hits a deadline.
Steps and UI details are based on platform versions at time of writing — check each platform for the latest interface.
Best for
Teams of 5–30 who manage projects in Wrike and need the rest of the team to see status changes in Slack without logging into Wrike.
Not ideal for
Teams with 100+ daily task updates — polling delay and task volume will create notification noise and Zapier costs will climb fast.
Sync type
real-timeUse case type
notificationReal-World Example
A 12-person product agency uses this to post into #client-projectname every time a Wrike task moves to 'In Review' or 'Completed.' Before the automation, the project manager manually pasted status updates into Slack twice a day, and developers regularly started work on tasks that were already blocked. Now the channel gets an automatic message within 15 minutes of any status change, and the PM sends zero manual updates.
What Will This Cost?
Drag the slider to your expected monthly volume.
Each platform counts differently — Zapier: 1 task per trigger. Make: 1 operation per module per record. n8n: 1 execution per run.





Prices shown for annual billing. Based on published pricing as of April 2026.
Estimated ROI
1000
min saved/mo
$583
labor value/mo
Free
no platform cost
Based on ~2 min manual effort per operation at $35/hr fully loaded labor cost.
Implementation
Before You Start
Make sure you have everything ready.
Field Mapping
Map these fields between your apps.
| Field | API Name | |
|---|---|---|
| Required | ||
| Task Title | ||
| Task Status | ||
| Permalink | ||
5 optional fields▸ show
| Assignee Name | |
| Due Date | |
| Project / Parent Folder Name | |
| Task Description | |
| Updated Date |
Step-by-Step Setup
Zapier Dashboard > Create Zap > Trigger > Search Apps
Create a new Zap and connect Wrike
Go to zapier.com and click 'Create Zap' in the left sidebar. The Zap editor opens to a blank canvas. In the Trigger box at the top, search for 'Wrike' and select it. You'll be choosing Wrike as the source that watches for task changes.
- 1Click 'Create Zap' in the left sidebar
- 2Click inside the Trigger box labeled 'Search for apps'
- 3Type 'Wrike' and select it from the dropdown
Trigger Panel > Choose Trigger Event
Choose the trigger event
In the 'Choose Trigger Event' dropdown, you have three relevant options: 'New Task', 'Task Status Changed', and 'Task Completed'. For the broadest coverage — status changes, completions, and deadline hits — select 'Task Status Changed'. This trigger fires whenever a task's status field updates in any direction, including to 'Completed'.
- 1Click the 'Choose Trigger Event' dropdown
- 2Select 'Task Status Changed'
- 3Click 'Continue'
Trigger Panel > Choose Account > Sign in to Wrike
Connect your Wrike account
Click 'Sign in to Wrike'. A popup window opens asking you to authorize Zapier. Log in with the Wrike account that has access to the projects you want to monitor. After approving, the popup closes and Zapier shows the connected account email. If your workspace has multiple Wrike accounts, confirm the right one is selected from the dropdown.
- 1Click 'Sign in to Wrike'
- 2Log in with your Wrike credentials in the popup
- 3Click 'Allow' to grant Zapier access
- 4Confirm the correct account appears in the dropdown and click 'Continue'
Trigger Panel > Set Up Trigger > Folder
Configure the trigger filter by folder or space
In the 'Set up trigger' panel, Zapier shows a 'Folder' field. Click the dropdown and select the specific Wrike folder or project you want to monitor. If you want to watch an entire Space, select the parent-level space folder. Leaving this blank monitors all tasks across the account — not recommended for busy workspaces because it will fire constantly.
- 1Click the 'Folder' dropdown
- 2Browse or search for your project folder by name
- 3Select the correct folder
- 4Click 'Continue'
Trigger Panel > Test Trigger
Test the Wrike trigger
Click 'Test trigger'. Zapier pulls the three most recently changed tasks from the selected folder. Review the sample data — you should see fields like task title, status, assignee name, permalink URL, and due date. Confirm these fields look correct before moving on. If no tasks appear, go into Wrike and change the status on any task in the folder, then re-run the test.
- 1Click 'Test trigger'
- 2Review the returned task fields in the sample data panel
- 3Confirm 'status', 'title', 'permalink', and 'assignee' fields are populated
- 4Click 'Continue with selected record'
Zap Editor > + Between Steps > Filter by Zapier
Add a Filter step to target specific statuses
Click the '+' button between the trigger and the action to add a Filter step. This prevents every minor status change from flooding your Slack channel. In the Filter setup, set the condition to: 'Task Status' — 'Contains' — then type the statuses you care about, such as 'Completed' or 'In Review'. Add OR conditions for each additional status. This way, only meaningful transitions post to Slack.
- 1Click the '+' icon between Trigger and Action
- 2Select 'Filter by Zapier' from the app list
- 3Set Field to 'Status' from the Wrike trigger data
- 4Set condition to '(Text) Contains'
- 5Type your target status value, e.g. 'Completed'
- 6Click 'Add OR condition' to add additional statuses like 'In Review'
- 7Click 'Continue'
Action Panel > Search Apps > Slack > Send Channel Message
Add Slack as the action app
Click the '+' below the Filter step to add an action. Search for 'Slack' and select it. From the 'Choose Action Event' dropdown, select 'Send Channel Message'. This posts a formatted message to a specific Slack channel every time a task clears the filter.
- 1Click the '+' button below the Filter step
- 2Type 'Slack' in the search box and select it
- 3Click the 'Choose Action Event' dropdown
- 4Select 'Send Channel Message'
- 5Click 'Continue'
Action Panel > Choose Account > Sign in to Slack
Connect your Slack workspace
Click 'Sign in to Slack'. A browser popup opens and asks you to choose your Slack workspace and authorize Zapier. The app requires permission to post messages — it does not read message history. After authorizing, your workspace name appears in the connected accounts dropdown. If your team has multiple Slack workspaces, confirm the right one is selected.
- 1Click 'Sign in to Slack'
- 2Select the correct Slack workspace from the dropdown
- 3Click 'Allow' to grant Zapier posting permissions
- 4Confirm the workspace name appears and click 'Continue'
Action Panel > Set Up Action > Channel / Message Text
Configure the Slack message
In the 'Set up action' panel, select the Channel where messages should post — pick the project-specific channel like #project-alpha. In the 'Message Text' field, build the notification using data from the Wrike trigger. Click inside the field and use the blue data pills to insert dynamic values. A clear message format is: '[Task Title] moved to [Status] — assigned to [Assignee Name]. View task: [Permalink URL]'.
- 1Click the 'Channel' dropdown and select your target Slack channel
- 2Click inside the 'Message Text' field
- 3Type your message prefix, e.g. '✅ Task update: '
- 4Click the blue '+' insert button and select 'Title' from Wrike data
- 5Add ' moved to ' and insert 'Status'
- 6Add ' — assigned to ' and insert 'Assignee Name'
- 7Add a new line and type 'View: ' then insert 'Permalink'
📬 New entry: {{1.name}}
Email: {{1.email}}
Details: {{1.description}}Action Panel > Set Up Action > Bot Name / Bot Icon / Emoji
Set bot name and icon
Scroll down in the action setup to find 'Bot Name' and 'Bot Icon'. Set the bot name to something recognizable like 'Wrike Updates' so team members know the source. For the icon, paste an emoji code like ':clipboard:' or a URL to a Wrike logo image. These fields are optional but make a big difference in channel readability when notifications stack up.
- 1Scroll to the 'Bot Name' field and type 'Wrike Updates'
- 2Click the 'Bot Icon' field and type ':clipboard:' or paste an image URL
- 3Leave 'Send as a Bot' toggled on
Action Panel > Test Action > Publish Zap
Test and publish the Zap
Click 'Test action' — Zapier sends a real message to the selected Slack channel using the sample Wrike data from step 5. Go into Slack and confirm the message appeared in the right channel with correct task title, status, assignee, and a working permalink. If the message looks right, click 'Publish Zap'. The Zap turns on and begins polling Wrike on your plan's schedule.
- 1Click 'Test action'
- 2Open Slack and navigate to the target channel
- 3Confirm the test message appeared with correct data
- 4Return to Zapier and click 'Publish Zap'
- 5Toggle the Zap to 'On' if it isn't already
This Code by Zapier step formats the due date from Wrike's ISO 8601 timestamp (e.g. '2024-11-15T00:00:00Z') into a human-readable string like 'Nov 15, 2024', and prepends a status-specific emoji to the message so each notification is visually scannable at a glance. Paste this as a 'Code by Zapier' step between the Filter step and the Slack action, then use the output variables 'formattedDueDate' and 'statusEmoji' as data pills in your Slack message field.
JavaScript — Code Step// Input data from Wrike trigger (set these as input fields in Code by Zapier)▸ Show code
// Input data from Wrike trigger (set these as input fields in Code by Zapier) const rawDueDate = inputData.dueDate; // e.g. '2024-11-15T00:00:00Z' const taskStatus = inputData.status; // e.g. 'Completed'
... expand to see full code
// Input data from Wrike trigger (set these as input fields in Code by Zapier)
const rawDueDate = inputData.dueDate; // e.g. '2024-11-15T00:00:00Z'
const taskStatus = inputData.status; // e.g. 'Completed'
// Format the due date into something readable
let formattedDueDate = 'No due date';
if (rawDueDate) {
const dateObj = new Date(rawDueDate);
const options = { month: 'short', day: 'numeric', year: 'numeric', timeZone: 'UTC' };
formattedDueDate = dateObj.toLocaleDateString('en-US', options); // 'Nov 15, 2024'
}
// Map status to a relevant emoji for quick visual scanning in Slack
const emojiMap = {
'Completed': '✅',
'In Review': '👀',
'In Progress': '🔄',
'Deferred': '⏸️',
'Cancelled': '❌'
};
const statusEmoji = emojiMap[taskStatus] || '📌';
// Return both values as output fields for use in the Slack message step
output = [
{
formattedDueDate: formattedDueDate,
statusEmoji: statusEmoji
}
];Going live
Production Checklist
Before you turn this on for real, confirm each item.
Troubleshooting
Common errors and how to fix them.
Frequently Asked Questions
Common questions about this workflow.
Analysis
Use Zapier for this if your team is non-technical and needs to set up the Wrike-to-Slack notification in under 30 minutes with no code. The guided Zap builder walks you through every field, the Wrike and Slack integrations are both first-class supported apps with reliable polling, and the Filter step is easy to configure without touching JSON or scripting. It also works fine for teams with fewer than 50 status changes per day — at that volume, the 15-minute poll delay is tolerable and costs stay low. If you need sub-2-minute notification speed or you're managing 10+ projects simultaneously, pick Make instead, which supports Wrike webhooks natively and fires in under 10 seconds.
Real cost math: each Wrike status change that passes your Filter = 1 Zapier task. A team running 2 projects with an average of 15 status changes per day hits 450 tasks/month. Zapier's free plan allows 100 tasks — you'll exceed it in one week. The Starter plan at $19.99/month gives you 750 tasks and 2-minute polling. Make's Core plan at $10.83/month gives you 10,000 operations and webhook-based triggers. For this specific workflow at moderate volume, Make is roughly half the price and faster. Zapier costs more but saves setup time if your team has never used automation before.
Make fires Wrike notifications via webhook in under 10 seconds and costs less — that's the honest case for switching. n8n, if you self-host, is free at any volume and supports Wrike via its HTTP node with full JSON control over the Slack block kit message format, which lets you build rich, formatted notifications instead of plain text. Power Automate has a Wrike connector but it's a premium connector requiring a $15/user/month Power Automate plan — not worth it just for this use case. Pipedream handles this well if you're comfortable with JavaScript and want webhook-speed triggers with a generous free tier. Zapier wins on ease of setup and the quality of its pre-built Wrike integration, but if cost or speed matters, Make is the better call.
Three things you'll hit after the Zap goes live. First, Wrike's API returns due dates in UTC ISO 8601 format ('2024-11-15T00:00:00Z') — if you paste that directly into the Slack message, your team will see an ugly timestamp. Use the Code step in this guide to format it before it hits Slack. Second, the polling gap means you'll occasionally see Slack messages arrive in batches — three notifications at once after a busy standup where everyone updates their tasks. This is unavoidable on Zapier without upgrading plans. Third, if anyone changes a task's title and status at the same time, Wrike may return two separate update events and the Zap fires twice. Filter narrowly to only the statuses your team actually cares about — that alone cuts noise by 60% in most projects.
Ideas for what to build next
- →Add a daily digest instead of per-event messages — Replace the per-event Slack message with a Zapier scheduled trigger that runs once per day, queries Wrike for all tasks changed in the last 24 hours, and posts a single summary to Slack. This cuts notification noise for busy projects.
- →Route notifications to different channels by project — Use Zapier Paths to check the Wrike folder name and post to a matching Slack channel — #project-alpha for one folder, #project-beta for another. One Zap handles all projects without duplication.
- →Add a reverse notification for Slack reactions — Build a second Zap that watches for a specific Slack emoji reaction (e.g. :white_check_mark:) on any Wrike notification message, then updates the corresponding Wrike task status to 'Approved'. This closes the loop without anyone logging into Wrike.
Related guides
How to Share Notion Meeting Notes to Slack with Pipedream
~15 min setup
How to Share Notion Meeting Notes to Slack with Power Automate
~15 min setup
How to Share Notion Meeting Notes to Slack with n8n
~20 min setup
How to Send Notion Meeting Notes to Slack with Zapier
~8 min setup
How to Share Notion Meeting Notes to Slack with Make
~12 min setup
How to Create Notion Tasks from Slack with Pipedream
~15 min setup