Monday.com Notifications Not Working? 8 Fixes for Bell, Email & Automation Alerts in 2026

When a monday.com status change goes unanswered for two days and the assignee swears they were never notified, the instinct is to blame the person. Don’t. In roughly nine out of ten cases I’ve audited for client workspaces, monday.com notifications not working traces back to one of three independent systems failing quietly: the in-app bell feed, the email delivery pipeline, or an automation notify recipe that stopped firing. Each system has its own settings, its own failure modes, and its own fix — and most troubleshooting advice online lumps them together, which is why teams toggle random settings for an hour and give up.

This guide separates the three failure modes and ranks eight fixes in diagnostic order, from the 30-second checks that solve most cases to the account-level blocks that require an admin or monday.com support. Every UI path below reflects the current 2026 interface, and the community-documented issues in Fixes 4, 6, and 7 link to the actual forum threads.

Monday.com Notifications Not Working: 3 Systems, 3 Failure Modes

Before you change anything, identify which system is broken. Getting this wrong is the number-one reason troubleshooting fails — people spend 40 minutes in profile settings when the real problem is a paused automation recipe that profile settings can’t touch.

• Bell (in-app) notifications — the bell icon in the left panel. These are generated when someone @mentions you, assigns you, replies to you, or subscribes you to an item. Failures here come from muted boards, browser/desktop permission blocks, or platform-side delays.
• Email notifications — a parallel copy of bell activity, sent from notifications@monday.com. These are controlled by a completely separate toggle table under My Profile → Notifications, and they fail at the toggle level or the deliverability level (spam, gateway filtering, bounce suppression).
• Automation notify recipes — “When status changes to Done, notify someone” style alerts. Critically, these are not governed by your bell or email preferences in the same way. A notify step that never fires is an automation problem: the recipe is off, the trigger condition wasn’t met, or a connected column was deleted. Monday.com’s own notifications via automations documentation treats these as a separate troubleshooting track.

Quick triage: if a colleague gets the alert and you don’t, it’s your settings or your mailbox (Fixes 1–4, 8). If nobody gets the alert from a specific recipe, it’s the automation (Fixes 5–6). If alerts arrive but behave badly — late, unclickable, or missing data — jump to Fixes 4, 6, and 7.

Fix 1: Turn Email Notifications Back On in My Profile

Email notifications are on by default for new accounts, but they get switched off more often than anyone admits — usually during an “inbox zero” purge months earlier that everyone forgot about. This is the first check in monday.com’s own email notifications guide, and it takes under a minute.

1. Profile picture (top-right corner) — click your avatar in the upper-right corner of any monday.com screen to open the account menu.
2. My Profile — select it from the dropdown to open your personal profile page.
3. Notifications tab — click it in the profile navigation. You’ll see a table of every notification event with columns for each delivery channel.
4. Email column — scan down the email column and re-enable the rows that matter: “I’m assigned to an item,” “Someone mentions me,” “I’m subscribed to an item,” and “A due date arrives.” Any unchecked row means monday.com is deliberately not emailing you for that event.
5. Notification frequency setting — while you’re here, confirm you haven’t switched emails to a daily digest; digest mode makes alerts look “missing” when they’re actually batched for later delivery.

Test it immediately: have a teammate @mention you in an item update. The bell should fire within seconds and the email within a few minutes. If the bell fires but no email ever lands, move to Fix 3 — your toggles are fine and the problem is deliverability.

Fix 2: Unmute the Board (“Mute All” Is the Silent Killer)

This is the fix that resolves the most baffling cases: notifications work perfectly on every board except one. Monday.com lets you mute notifications per board, and the setting is invisible in daily use — there’s no banner, no muted-bell icon on the board header, nothing. Someone mutes a noisy board during a busy sprint, forgets, and three months later “monday.com is broken.”

1. Open the affected board — this setting is per-board, so you must be on the exact board where alerts have gone quiet.
2. Three-dot menu (⋯) at the top right of the board — click it to open the board options menu.
3. Board notification settings — select this option to see the board’s alert level.
4. Check for “Mute all” — if it’s selected, every bell and email alert from this board is suppressed for you, regardless of your profile settings. Switch back to the default (all activity) or the important-only middle tier.
5. Repeat on other quiet boards — mute settings don’t sync across boards, so audit each board where you’ve noticed silence.

Note the hierarchy here: board-level mute overrides profile-level settings. You can have every toggle in Fix 1 enabled and still hear nothing from a muted board. Monday.com support lists this as the second check in its assignment-notification checklist for exactly that reason.

Fix 3: Whitelist monday.com Senders Against Spam Filters

If your in-app bell works but emails never arrive — and your toggles are on — the emails are almost certainly being sent and then intercepted. Monday.com’s “Not receiving emails” support article covers this scenario, and it’s especially common on corporate Google Workspace and Microsoft 365 tenants where an email gateway quarantines bulk senders before they ever reach your junk folder.

1. Spam/Junk folder — search your spam folder for “monday.com”. If alerts are there, mark them “Not spam” and move to the next step so it sticks.
2. Add notifications@monday.com to contacts — in Gmail or Outlook, adding the sender as a contact is the fastest personal-level whitelist.
3. Mailbox filter rule — create a rule: if the sender contains monday.com, never send to spam (Gmail: Settings → Filters and Blocked Addresses → Create filter → “Never send it to Spam”; Outlook: Settings → Mail → Junk email → Safe senders and domains).
4. Admin-level allowlist — if the whole company is affected, your IT admin needs to whitelist the monday.com sending domain at the gateway (Google Admin Console → Apps → Google Workspace → Gmail → Spam, Phishing and Malware; Microsoft 365 Defender → Policies → Anti-spam → Allowed senders/domains). Entire teams losing monday.com email at once is a gateway problem, not a user problem.
5. Check for a full mailbox or auto-forwarding rules — bounced deliveries from a full inbox or a misfiring forward rule can land you on monday.com’s suppression list (see Fix 8).

If you administer other tools too, the same gateway allowlist pass is worth doing across platforms — we’ve documented the equivalent processes in our Asana notifications troubleshooting guide and Smartsheet notifications fix guide.

Fix 4: Fix Bell, Browser & Delayed In-App Notifications

The reverse scenario: emails arrive fine, but the bell counter never updates, desktop pop-ups don’t appear, or in-app alerts show up 20 minutes late. Delayed and missing in-app notifications are a recurring community complaint — threads like “Notifications not appearing right away” document alerts that only surface after a page refresh. Here’s the sequence that resolves it.

1. My Profile → Notifications → Desktop column — confirm desktop notifications are enabled for the events you care about, in the same table you used in Fix 1.
2. Browser site permissions — in Chrome or Edge, click the padlock/tune icon in the address bar while on monday.com → Site settings → Notifications → set to “Allow.” If the browser blocks the permission, monday.com cannot push desktop pop-ups no matter what its own settings say.
3. Operating system focus mode — check Windows Focus Assist / Do Not Disturb (Settings → System → Notifications) or macOS Focus. OS-level DND suppresses monday.com pop-ups while the bell counter silently increments.
4. Hard refresh the session — if bell alerts appear only after reloading, your websocket session has gone stale. Press Ctrl+Shift+R (Cmd+Shift+R on Mac), or fully log out and back in. On the desktop app, quit and relaunch rather than just closing the window.
5. Clear cache or test incognito — persistent delays that survive a refresh usually clear after wiping site data (browser Settings → Privacy → Clear browsing data → Cached images and files). Test in an incognito window first to confirm the cache is the culprit.
6. Check monday.com’s status page — platform-wide notification delays do happen; visit status.monday.com before spending more time on local fixes. If the platform reports degraded notification delivery, there is nothing to fix on your end.

Fix 5: Repair Notify Automations That Never Fire

This is where most troubleshooting goes off the rails. A “When status changes to something, notify someone” recipe that stops sending has nothing to do with Fixes 1–4. No profile toggle disables an automation, and no automation is revived by whitelisting an email address. A silent notify step means the trigger never fired or the recipe is off — treat it like any other broken automation.

1. Automate button (top right of the board) — open the Automations Center for the affected board.
2. Board automations tab → recipe toggle — find the notify recipe and confirm its on/off switch is actually on. Recipes get paused during board maintenance and never re-enabled; they also deactivate when their owner leaves the account.
3. Automation activity log — open the activity view inside the Automations Center and search for the recipe. If it shows successful runs, the automation is fine and your problem is delivery (go back to Fixes 1–4). If there are no runs at all, the trigger never fired. If runs show errors, read the error — it usually names the broken column or missing recipient.
4. Trigger conditions — open the recipe and verify each condition against reality: does the status column still contain the exact label the trigger watches? Renamed or recolored labels break status-based triggers, and a recipe watching “Done” won’t fire on “Complete.” Also confirm any “only if” conditions are actually met by your test item.
5. Connected columns and boards — a deleted or changed column referenced by the recipe (the trigger column, a people column used as the recipient, or a linked board) disables the run silently. Rebuild the recipe pointing at the current columns.
6. Recipient definition — if the recipe notifies a people column that’s empty on the item, no one gets notified and no error appears. Check the item actually has a person in that column at the moment the trigger fires.

For deeper trigger debugging — sequencing, quota exhaustion, cross-board automations — see our full Monday.com automations troubleshooting guide, and if you’re building recipes from scratch, the no-code automations setup guide covers recipe anatomy in detail.

Fix 6: Fix Notify Messages With Blank Item Fields

A distinct 2026-relevant failure: the notify automation fires, the notification arrives, but the message reads “Task is now — due ” with the item fields missing. Community threads such as “Major Notification Issue — not populating fields from board items” document dynamic placeholders failing to resolve. This is a recipe-configuration problem, and it has a reliable fix path.

1. Open the recipe’s notify message — in the Automations Center, click the recipe and open the “notify” step to view the message template with its column placeholders (e.g., {item name}, {status}).
2. Check for unsupported column types — Formula, Auto Number, Progress, Dependency, and Link to Item columns are not supported in the notify field. A placeholder pointing at one of these will render blank or break the message. Replace it with a supported column, or mirror the value into a text column first.
3. Re-insert placeholders from the picker — delete the broken placeholder tokens and re-add them by selecting columns from the automation’s field picker rather than typing braces manually. Hand-typed tokens that don’t exactly match the column reference silently fail.
4. Verify the column has a value at trigger time — if the automation fires the instant an item is created, columns filled a second later were empty when the message was built. Change the trigger, or add the data before the triggering event.
5. Rebuild the recipe if placeholders still won’t resolve — community-confirmed workaround: delete the recipe and recreate it from scratch. Recipes carried across renamed or restructured columns can hold stale internal references that only a rebuild clears.

Fix 7: Fix Notification Links That Don’t Open the Item

The notification arrives but clicking it goes nowhere — or lands on the board without opening the item card. Dead deep links are documented in threads like “Links to the task in notifications and inbox don’t work”, with subitem links and the desktop app the most frequent offenders. Work through this order.

1. Test the same link in a browser — if a link that fails in the desktop app opens fine in Chrome, the issue is the app’s link handling, not the notification. Update the desktop app to the latest version, or use the browser until the app is patched.
2. Clear cache and re-authenticate — deep links fail to resolve when your session token is stale; the link loads, hits an auth wall, and dumps you on a generic page. Log out, clear site data for monday.com, and log back in.
3. Check whether the target is a subitem — subitem deep links are a known weak spot: they may open the parent item’s update section instead of the subitem itself. Once on the parent item, expand the subitems section manually. If precision matters for your workflow, have automations reference the parent item instead.
4. Confirm you still have access to the item — links to items on boards you’ve been removed from, or on private boards you were never shared into, resolve to nothing or an error. Ask the board owner to confirm your access, especially after workspace permission restructures.
5. Check whether the item was deleted or archived — notifications outlive their items. A link to an archived item won’t open normally; an admin can check Archive/Trash under the board menu and restore the item if it’s needed.

Fix 8: Clear Guest, Bounce-List & Account-Level Blocks

If everything above checks out and one specific person still gets nothing, the block is at the account level. These cases need an admin — or monday.com support — but they’re quick once you know what to ask for.

1. Verify guest access and board sharing — guests only receive notifications from boards explicitly shared with them. An admin should confirm the guest’s account is active and the shareable board actually lists them (board three-dot menu → Board members / sharing settings).
2. Ask support to check the email suppression list — if your mailbox ever hard-bounced a monday.com email (full inbox, changed address, aggressive gateway rejection), the address can be suppressed from future sends. No setting on your side fixes this; contact monday.com’s 24/7 support via the question-mark icon → Contact us and ask them to clear your address from the bounce list.
3. Confirm the profile email is current — under your avatar → My Profile → Personal info, check the email on file. Post-migration accounts and rebranded domains frequently leave notifications flowing to a dead address.
4. Check admin-level restrictions — on Enterprise accounts, admins can restrict features and integrations account-wide. If notifications died for everyone after a security review, ask the admin what changed under Admin → Security.
5. Test with a personal email — as a definitive isolation test, an admin can invite a personal Gmail address to the workspace. If that address receives alerts instantly, the problem is 100% your corporate email infrastructure — take Fix 3’s admin steps to IT with the evidence.

Still Have Monday.com Notifications Not Working? Escalation Checklist

Before escalating, capture the evidence that gets support tickets resolved in one pass instead of five: which system fails (bell, email, or automation), whether it fails for one user or everyone, one concrete example (item URL, expected notification, timestamp), and a screenshot of the automation activity log if a recipe is involved. Monday.com support is available 24/7 and can see server-side delivery logs you can’t — the bounce list, send attempts, and automation execution errors.

It’s also worth confirming the problem is actually monday.com. If your team recently added integrations that mirror alerts into chat, notification fatigue and channel confusion can masquerade as “missing” alerts — a pattern we see with the monday.com Microsoft Teams integration when the same event notifies in two places and users mute one of them.

Frequently Asked Questions

Why do I get bell notifications but no emails from monday.com?

Bell and email are separate delivery channels with separate toggles. If the bell works, monday.com is generating the notification correctly — so the email is either disabled in My Profile → Notifications (email column), batched into a digest, or being intercepted by your spam filter or corporate email gateway. Check the toggle first, then whitelist notifications@monday.com per Fix 3.

Does muting a board stop automation notifications too?

Board notification settings control the activity alerts you receive from that board, and “Mute all” suppresses them entirely for you. Automation notify recipes are configured and triggered independently — but if you’ve muted the board or disabled the relevant channels in your profile, alerts a recipe generates can still fail to reach you. That’s why the diagnostic order matters: confirm the recipe ran via the activity log, then check your delivery settings.

How do I check whether a monday.com automation actually ran?

Open the board, click Automate in the top-right corner, and view the automation activity log inside the Automations Center. It lists every run with a timestamp and status. A successful run means your problem is notification delivery, not the automation; no run means the trigger conditions were never met; a failed run shows an error identifying the broken column or recipient.

Why do monday.com notification links not open the item?

The usual causes are a stale login session, an outdated desktop app, a link pointing at a subitem (which may open the parent item instead), or an item you no longer have access to because it was moved to a private board, archived, or deleted. Test the link in a browser first — if it works there, update or reinstall the desktop app.

Do viewers and guests receive monday.com notifications?

Yes, but only for boards they can access. Guests must be explicitly invited to each shareable board, and their notifications stop the moment that sharing is removed or their account is deactivated. If a guest reports silence, the board owner should re-confirm the guest appears in the board’s sharing settings before troubleshooting anything else.