Chrome notifications not working? Fix silent alerts

This guide covers Tab Automation extension alerts. For notifications from a website such as Gmail, start with Chrome’s website notification settings.

For a silent extension alert, click Test on Desktop notification on the Send Alert step first. If that test is silent, check Chrome’s operating-system notification permission, Focus or Do Not Disturb, and the desktop toggle.

If the desktop Test works but an automation run does not, the OS path is already working. Check whether the runner actually reaches Send Alert.

1. Run Test

1. Open the side panel. In Library → Yours, open the automation to edit its Send Alert settings. An Active Job opens read-only Details; use Edit in Library to open its recipe.
2. Expand Send Alert.
3. Turn on Desktop notification to verify the banner, or Sound to verify the chime.
4. Click Test on that output only. Desktop Test does not play the chime; Sound Test does not show a banner.
5. Look for the banner in the desktop notification center, or listen for the Tab Automation chime.

Test notification copy may use an example host; it does not need the rest of the automation to run.

Webhook has its own Test pill. It POSTs only to destinations selected on that step and does not use Chrome’s OS notification permission. If the desktop banner is silent, stay on the OS steps below. If a webhook is rejected or times out, open Activity for the redacted delivery line. Setup for Slack, Discord, or ntfy is in send a Slack webhook when a Chrome page changes.

Repeat Each cycle and When it stops have the same per-output Test buttons.

If the extension reports that notifications are disabled in browser or system settings, continue with the OS checks.

2. Allow Google Chrome in the operating system

Tab Automation uses Chrome’s extension notification API. The operating system still decides whether Google Chrome can show a banner.

macOS

Open System Settings → Notifications → Google Chrome. Allow notifications and choose a visible alert style. Apple’s Notifications settings guide explains banners, sounds, and Notification Center delivery.

If a Focus mode is active, temporarily turn it off for the test or allow Chrome in that Focus.

Windows

Open Settings → System → Notifications. Enable notifications globally and for Google Chrome, including banners and notification-center delivery. Microsoft’s notification settings guide covers Windows 10 and 11.

On Windows 11, check Do not disturb, which Focus can enable automatically. Turn it off for the test or allow Chrome through priority notifications. Older Windows versions may call the control Focus assist.

Linux

Notification controls depend on your desktop environment. In GNOME, check Settings → Notifications, enable Chrome’s notifications, and turn off Do Not Disturb for the test. The GNOME notification guide covers these controls. For another desktop, use its notification settings and documentation.

After any OS change, keep Chrome open and click Test on Desktop notification again.

3. If desktop Test works but the run does not

A successful desktop Test proves that the banner path can work. It does not prove that the automation reaches the step.

Check these in order:

1. Confirm the graph contains Send Alert. If / Else does not send alerts by itself.
2. Confirm Desktop notification, Sound, or both are enabled on that step.
3. If Send Alert is inside Then or Else, verify that the condition follows the expected branch.
4. Open Activity and check whether Send Alert ran, was skipped because the other branch ran, or the automation stopped earlier.
5. If Wait Until comes first, check Pause when this wait succeeds. With it enabled, success pauses before the alert. A timeout continues to later steps. Review Activity to distinguish the two.

For a notification only after a match, place Send Alert in the matching If / Else branch. For an unconditional alert at a particular point, place it directly in that sequence.

Repeat’s Each cycle and When it stops alerts are separate controls on the End block. They remain off until enabled.

4. If the banner works but sound does not

First make sure Sound is enabled on Send Alert. A desktop banner can be on while the Tab Automation sound is off, and sound can be on without a desktop notification.

Then check system output volume, the selected audio device, app or notification volume controls, and mute state. The Tab Automation chime is a separate sound output from the operating system’s notification sound. On Windows or Linux, check any per-app volume control exposed by the OS or desktop.

Click Test on Sound after each audio change, and Test on Desktop notification if the banner is still missing. If you hear the chime but do not see a banner, return to Chrome’s OS notification permission and Focus settings.

5. Confirm the fix

Use this short success check:

• Test on Desktop notification shows a banner. Test on Sound plays the chime. Each Test button fires only its own output.
• Check the notification center for a missed banner if your desktop is configured to retain it.
• A simple graph with Send Alert reaches that step and records it in Activity.
• Your real graph reaches the intended branch or point and produces the same output.

Chrome’s website notification settings are a different switch. They control prompts and notifications from websites; Tab Automation extension alerts do not use a site’s permission prompt. Chrome’s general notification help is useful when webpage notifications are also failing.

To choose between a timer, a one-time condition check, and polling for a later change, read auto refresh vs page monitor.