Beginner~8 min setupCommunication & Project ManagementVerified April 2026
Slack logo
Monday.com logo

How to Send Monday.com Status Alerts to Slack with Zapier

Automatically sends a Slack message to a specified channel whenever a Monday.com item changes status, is created, 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

Small to mid-size teams who want instant Slack alerts when Monday.com item statuses change without writing any code.

Not ideal for

Teams with high Monday.com update volume (100+ items/day) — at that scale, Make handles the same workflow for a fraction of the task cost.

Sync type

real-time

Use case type

notification

Real-World Example

💡

A 12-person product team at a SaaS company uses this to post to #product-updates in Slack whenever a Monday.com task moves to 'In Review' or 'Done'. Before this, the PM pinged developers manually on Slack to announce status changes — which meant delays of 30–90 minutes when they were heads-down. Now the message fires within 15 minutes of the status change and tags the item owner automatically.

What Will This Cost?

Drag the slider to your expected monthly volume.

/mo
505005K50K

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.

Monday.com account with at least Viewer access to the board you want to monitor — Editor or higher is needed if you plan to update items back
Slack account with permission to post to the target channel — you must be a member of private channels before Zapier can post to them
Zapier account — free tier works for basic setup but limits polling to every 15 minutes; paid plans poll every 2 minutes
At least one recent status change on your Monday.com board so Zapier can pull sample data during the trigger test
Monday.com API access enabled — confirm your Monday.com plan includes API access (Standard plan and above)

Field Mapping

Map these fields between your apps.

FieldAPI Name
Required
Item Name
Column Value (New Status)
Pulse URL
6 optional fields▸ show
Previous Column Value
Board Name
Group Name
Item Owner / Person Column
Due Date
Changed At (Timestamp)

Step-by-Step Setup

1

zapier.com > Dashboard > Create Zap

Create a new Zap in Zapier

Log in to zapier.com and click the orange 'Create Zap' button in the left sidebar. The Zap editor opens with two empty blocks: Trigger and Action. You'll build the Monday.com trigger first. Give the Zap a name at the top — something like 'Monday Status → Slack' — so it's easy to find later.

  1. 1Log in at zapier.com
  2. 2Click 'Create Zap' in the left sidebar
  3. 3Click the name field at the top and type 'Monday Status → Slack'
  4. 4Click the empty Trigger block to begin setup
What you should see: The Zap editor opens with a Trigger block and an Action block visible. The trigger block shows 'Choose App & Event' in gray text.
2

Zap Editor > Trigger > App & Event

Select Monday.com as the trigger app

In the Trigger block, type 'Monday' into the app search field. Select 'Monday.com' from the results — it shows the Monday.com rainbow logo. You'll then choose a trigger event. For status changes, select 'Column Values Changed'. This trigger fires whenever any column value on a Monday.com item is updated, including the Status column.

  1. 1Click inside the 'Search for an app' field in the Trigger block
  2. 2Type 'Monday' and press Enter
  3. 3Click 'Monday.com' from the dropdown list
  4. 4Click the 'Trigger Event' dropdown
  5. 5Select 'Column Values Changed'
What you should see: The Trigger block now shows 'Monday.com' with the event 'Column Values Changed' listed beneath it. A 'Continue' button appears at the bottom of the block.
Common mistake — Monday.com also offers a 'Status Column Changed' trigger in some Zapier accounts — if you see it, use that instead. It's more precise and only fires on status columns, not every column update.
Zapier
+
click +
search apps
Slack
SL
Slack
Select Monday.com as the tri…
Slack
SL
module added
3

Zap Editor > Trigger > Account

Connect your Monday.com account

Click 'Sign in to Monday.com' and a new browser window opens asking you to authorize Zapier. Log in with your Monday.com credentials and click 'Allow'. Zapier needs permission to read your boards and item data. Once authorized, the window closes and you return to the Zap editor with your account listed.

  1. 1Click 'Sign in to Monday.com'
  2. 2Log in with your Monday.com credentials in the popup window
  3. 3Click 'Allow' to grant Zapier read access
  4. 4Return to the Zap editor and confirm your account name appears
What you should see: Your Monday.com account email address appears in the Account field with a green checkmark. The 'Continue' button becomes active.
Common mistake — Zapier connects to Monday.com using your personal account credentials. If you're on a Monday.com Enterprise plan with SAML SSO, the OAuth popup may fail. In that case, use a service account or ask your IT admin to whitelist Zapier.
Zapier settings
Connection
Choose a connection…Add
click Add
Slack
Log in to authorize
Authorize Zapier
popup window
Connected
green checkmark
4

Zap Editor > Trigger > Configure

Configure the Monday.com trigger settings

Zapier now asks you to choose which Monday.com board and column to watch. Select the board where your project items live from the 'Board' dropdown — Zapier pulls the list directly from your workspace. In the 'Column ID' field, select your Status column (it usually appears as 'Status' or a custom name your team set). Leave the 'Group' field blank unless you only want to watch a specific group on the board.

  1. 1Click the 'Board' dropdown and select your target board
  2. 2Click the 'Column ID' dropdown and select your Status column
  3. 3Optionally select a specific Group if you want to limit scope
  4. 4Click 'Continue'
What you should see: The configure section shows your board name and column name filled in. No red error indicators are visible.
Common mistake — If your board has multiple Status columns (e.g., 'Priority' and 'Stage'), the dropdown lists them all. Pick the wrong one and your Zap fires on the wrong updates. Check the column name in Monday.com first by hovering over the column header.
5

Zap Editor > Trigger > Test

Test the Monday.com trigger

Click 'Test trigger' and Zapier polls Monday.com for recent items where the status column changed. It pulls up to 3 recent records. You'll see a list of sample data including the item name, previous value, new value, and board ID. Expand one record to verify the fields look correct — especially confirm that 'Column Value' contains an actual status label like 'In Progress' or 'Done', not a numeric ID.

  1. 1Click 'Test trigger'
  2. 2Wait 5–10 seconds for Zapier to fetch sample data
  3. 3Click on a sample record to expand its fields
  4. 4Confirm 'Column Value' shows a readable status label
What you should see: Zapier displays 1–3 sample Monday.com records with field names on the left and values on the right. You can see fields like 'Item Name', 'Column Value', 'Board Name', and 'Created At'.
Common mistake — If the test returns 'We couldn't find any samples', it means no status changes happened recently on that board. Manually change a status in Monday.com, wait 2 minutes, then click 'Test trigger' again.
Zapier
▶ Turn on & test
executed
Slack
Monday.com
Monday.com
🔔 notification
received
6

Zap Editor > + Between Steps > Filter by Zapier

Add a Zapier Filter step to target specific statuses

Click the '+' icon between the Trigger and Action blocks to insert a Filter step. This lets you fire the Slack message only when the status changes to a value you care about — like 'Done' or 'Blocked' — not every single update. In the Filter setup, set the condition to: 'Column Value' → 'Contains' → type your target status (e.g., 'Done'). Without this filter, every column value change on that board fires a Slack message.

  1. 1Click the '+' icon between the Trigger and Action blocks
  2. 2Click 'Filter' from the step type options
  3. 3Set field to 'Column Value' from the Monday.com trigger
  4. 4Set condition to 'Contains'
  5. 5Type your target status label, e.g., 'Done'
  6. 6Click 'Continue'
What you should see: The Filter step shows a green 'Your Zap would have continued' message confirming the sample data matches your condition.
Common mistake — The Filter step costs one Zapier task every time it runs — even when the filter fails and the Zap stops. If your board sees 500 status changes/month and you filter for only 50, you still burn 500 tasks.
Slack
SL
trigger
filter
Status
matches criteria?
yes — passes through
no — skipped
Monday.com
MO
notified
7

Zap Editor > Action > App & Event

Add Slack as the action app

Click the Action block and search for 'Slack'. Select it and choose 'Send Channel Message' as the action event. This posts a message to any public or private Slack channel your connected account can access. Click 'Continue' to move to account setup.

  1. 1Click the Action block
  2. 2Type 'Slack' in the app search field
  3. 3Select 'Slack' from the results
  4. 4Click the 'Action Event' dropdown
  5. 5Select 'Send Channel Message'
  6. 6Click 'Continue'
What you should see: The Action block shows 'Slack' with 'Send Channel Message' as the selected event. The account connection step is now visible.
8

Zap Editor > Action > Account

Connect your Slack workspace

Click 'Sign in to Slack'. A Slack OAuth window opens asking which workspace to connect. Select your workspace, then click 'Allow'. Zapier requests the 'chat:write' scope to post messages. If your Slack admin has restricted OAuth app installs, you may see a 'Needs Approval' screen — you'll need to request admin approval before the connection completes.

  1. 1Click 'Sign in to Slack'
  2. 2Select your workspace from the dropdown in the OAuth popup
  3. 3Click 'Allow' to grant posting permissions
  4. 4Confirm your workspace name appears in the Account field
What you should see: Your Slack workspace name appears in the Account field with a green checkmark. No error messages are visible.
Common mistake — Zapier posts messages as its own bot user ('Zapier'), not as you. The message will show 'Zapier' as the sender in Slack. If your team needs messages to appear from a specific person, use a Slack bot token in a custom integration instead.
9

Zap Editor > Action > Configure

Configure the Slack message content

In the Action configuration, select the Slack channel from the 'Channel' dropdown — type '#' to filter by channel name. In the 'Message Text' field, build your notification by inserting Monday.com fields using Zapier's field picker. Click inside the message field and type your template, using the blue '+' button to insert dynamic values. A clear message format includes the item name, the new status, and a link back to the Monday.com board.

  1. 1Click the 'Channel' dropdown and select your target channel (e.g., #project-updates)
  2. 2Click inside the 'Message Text' field
  3. 3Type a message like: '📋 *' then insert the 'Item Name' field
  4. 4Continue typing: '* moved to *' then insert the 'Column Value' field
  5. 5Add a final line with 'Board: ' and insert the 'Board Name' field
  6. 6Optionally set 'Bot Name' to something like 'Monday Updates'
What you should see: The Message Text field shows a mix of static text and blue dynamic field pills. The preview shows a realistic-looking Slack message with your Monday.com data filled in.
Common mistake — Monday.com's 'Pulse URL' field (the direct link to the item) is buried in the trigger data — scroll down the field picker to find 'Pulse URL' and add it to your message. Without it, team members have no quick way to jump to the item.
Message template
📬 New entry: {{1.name}}
Email: {{1.email}}
Details: {{1.description}}
10

Zap Editor > Action > Test

Test the Slack action

Click 'Test action' and Zapier sends a real test message to your selected Slack channel using the sample Monday.com data from Step 5. Open Slack and check the channel immediately — the message should appear within 30 seconds. Review the formatting: confirm the status label is readable, the item name is correct, and any links work. If the formatting looks off, go back and adjust the message text.

  1. 1Click 'Test action'
  2. 2Open Slack and navigate to your selected channel
  3. 3Confirm the test message arrived
  4. 4Click any links in the message to verify they work
  5. 5Go back and edit the message format if anything looks wrong
What you should see: A Slack message from 'Zapier' (or your custom bot name) appears in the channel with the Monday.com item name, status, and board name filled in correctly.
11

Zap Editor > Publish

Turn on the Zap and set a name

Click 'Publish Zap' in the top right corner. Zapier confirms the Zap is live and shows a toggle switch in the 'on' position. The Zap now polls Monday.com for status changes approximately every 2 minutes on a paid Zapier plan, or every 15 minutes on the free tier. Note that polling frequency — not webhooks — determines how quickly your team sees the notification in Slack.

  1. 1Click 'Publish Zap' in the top right corner
  2. 2Confirm the success screen appears
  3. 3Click 'View Zap' to see it in your Zap dashboard
  4. 4Confirm the toggle is in the 'On' position
What you should see: The Zap appears in your dashboard with a green 'On' toggle and shows 'Monday.com → Filter → Slack' as the step summary.
Common mistake — Zapier's Monday.com trigger uses polling, not a real-time webhook. On the free plan, expect up to 15 minutes between a status change and the Slack message. Upgrade to a paid plan to get 2-minute polling.

This Code by Zapier step reformats the raw Monday.com timestamp into a human-readable date and automatically prepends an emoji to the status label in the Slack message — so 'Done' becomes '✅ Done' and 'Blocked' becomes '🚫 Blocked'. Add a 'Code by Zapier' step between your Filter and the Slack action, select JavaScript, and paste this in.

JavaScript — Code Step// Inputs from previous Zapier steps:
▸ Show code
// Inputs from previous Zapier steps:
// inputData.status — the new status value from Monday.com
// inputData.changedAt — the ISO timestamp of the change

... expand to see full code

// Inputs from previous Zapier steps:
// inputData.status — the new status value from Monday.com
// inputData.changedAt — the ISO timestamp of the change
// inputData.itemName — the name of the Monday.com item

const statusEmojis = {
  'Done': '✅',
  'In Progress': '🔄',
  'Blocked': '🚫',
  'In Review': '👀',
  'Stuck': '⛔',
  'Working on it': '🔧'
};

const status = inputData.status || 'Unknown';
const emoji = statusEmojis[status] || '📋';
const labeledStatus = `${emoji} ${status}`;

// Format timestamp: '2024-08-10T14:32:00Z' → 'Aug 10, 2024 at 2:32 PM'
let formattedDate = 'No date';
if (inputData.changedAt) {
  const d = new Date(inputData.changedAt);
  formattedDate = d.toLocaleString('en-US', {
    month: 'short',
    day: 'numeric',
    year: 'numeric',
    hour: 'numeric',
    minute: '2-digit',
    hour12: true
  });
}

output = [
  {
    labeledStatus: labeledStatus,
    formattedDate: formattedDate,
    itemName: inputData.itemName || 'Unnamed item'
  }
];

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

VerdictWhy Zapier for this workflow

Use Zapier for this if your team has no developer resources and wants the notification working in under 20 minutes. The guided Zap builder makes it hard to misconfigure the Slack action, the Monday.com trigger is well-documented, and the Filter step handles basic conditional logic without any code. The one scenario where you should skip Zapier: if you need the Slack message to arrive within 30 seconds of a status change. Zapier polls Monday.com — it doesn't receive webhooks from it — so the minimum delay is 2 minutes on paid plans and 15 minutes on free. For real-time needs, Make is the right call.

Cost

The math on cost: each status change that passes through the Zap burns 3 tasks — 1 for the trigger poll, 1 for the Filter, 1 for the Slack message. If your team changes statuses 200 times per month, that's 600 tasks. Zapier's free plan gives you 100 tasks/month, so you'll need a paid plan. The Starter plan costs $19.99/month and includes 750 tasks — enough for that volume. Make's free plan covers 1,000 operations/month at no cost, and Monday.com status changes on Make use webhooks, not polling, so you're not burning operations on failed filter checks. For 200 status changes/month, Make is free and Zapier costs $19.99.

Tradeoffs

Here's how the competitors compare on this specific use case. Make has native Monday.com webhook support — the Slack message fires in seconds, not minutes, and the built-in Router module handles channel routing by board or status without extra task costs. n8n lets you self-host the entire workflow, connect to Monday.com's full GraphQL API, and add conditional logic with zero per-task fees — the right choice if your team has a developer and cares about cost at scale. Power Automate is the right pick if your company is already in Microsoft 365 and your team lives in Teams, not Slack — but its Monday.com connector is limited compared to Zapier's. Pipedream gives you full code control and Monday.com webhook support with 10,000 free invocations/month. Zapier wins here specifically because the setup is the fastest and requires zero technical knowledge — if your team will configure and maintain this themselves without IT involvement, Zapier is the right tool.

Three things you'll hit after setup. First, Monday.com status labels are case-sensitive in Zapier's Filter step — if your board uses 'done' and you typed 'Done' in the filter, it silently drops every event. Double-check capitalization before going live. Second, Monday.com logs multiple change events when its own automations cascade after a manual status update — you can get 2–3 Slack messages for a single human action. Add a timestamp filter as described in troubleshooting to reduce this. Third, the 'Pulse URL' field that Zapier exposes points to the item, but Monday.com's URLs require the user to be logged in — guests or external stakeholders clicking the link will hit a login wall. If you share Slack channels with clients, mention the board name and item name in plain text rather than relying solely on the link.

Ideas for what to build next

  • Add Deadline Reminders with a Second ZapBuild a separate Zap using the Monday.com 'Upcoming Due Date' trigger to send a Slack reminder 24 hours before an item's deadline. This pairs with the status change Zap to give the team both progress updates and deadline alerts.
  • Route Notifications to Different Slack Channels by BoardAdd a Zapier Paths step to send messages to different Slack channels based on which Monday.com board triggered the event — engineering updates go to #eng-updates, design updates to #design-updates. This prevents all notifications from flooding a single channel.
  • Create a Weekly Digest Instead of Per-Change AlertsBuild a separate scheduled Zap that runs every Monday morning, queries Monday.com for all items in 'Blocked' or 'Stuck' status, and posts a single digest message to Slack. This reduces notification noise for teams that find per-change alerts too frequent.

Related guides

Was this guide helpful?
Slack + Monday.com overviewZapier profile →