A practical field guide from Automation Ace.
Short answer: to get notified when a Claude Code scheduled task (formerly a routine) runs, open the task at claude.ai/code/routines, choose Edit, expand Advanced settings, open the Notifications tab, turn on Notify me when this scheduled task finishes, and check Push notification, Email, Slack, or any combination. Claude sends a one-line summary when each run completes. For tasks that watch for a condition, it only notifies you when there is something worth telling you. Install the Claude mobile app for push, and make the end of your prompt say exactly what the summary should contain.
Notification settings for scheduled tasks were new at the time of writing, and labels in your account may differ slightly (one report calls the toggle “Notify me when this task is completed”). Scheduled tasks are in research preview, so check the Claude Code documentation for changes.
Short answer
- Open the task → Edit → Advanced settings → Notifications.
- Turn on Notify me when this scheduled task finishes.
- Check Push notification, Email, and/or Slack.
- For push, install the Claude app and allow notifications.
- End the prompt with a clear one-line result, or “nothing to report” rules for watch tasks.
- Click Run now to test each channel.
The notification settings
The task's Advanced settings panel has four tabs: General (repository, environment), Connectors, Behavior, and Notifications. The Notifications tab holds:
| Setting | Where | What it does |
|---|---|---|
| Notify me when this scheduled task finishes | Edit → Advanced settings → Notifications | Turns on a one-line summary when each run completes |
| Push notification | Same tab, checkbox | Sends the summary to the Claude mobile app on your phone |
| Same tab, checkbox | Sends the summary to your account's email | |
| Slack | Same tab, checkbox | Sends the summary to you in Slack |
The setting is per task. A nightly report and a critical alert check can notify you in different ways.
How to turn on notifications
- Go to claude.ai/code/routines (or Scheduled in the Desktop app's Code tab) and open the task.
- Open the menu next to the task's name and choose Edit. For a new task, the same settings are in the creation dialog.
- Expand Advanced settings and select the Notifications tab.
- Turn on Notify me when this scheduled task finishes.
- Check the channels you want: Push notification, Email, Slack.
- Click Save changes.
New to scheduled tasks? Start with how to run a Claude Code agent on a schedule and on demand.
Push, email, or Slack: which to choose
| Channel | You need | Best for | Watch out for |
|---|---|---|---|
| Push | The Claude app on iOS or Android, signed in to the same account, with OS notifications allowed | Knowing right away, wherever you are | Focus modes, notification summaries, and battery optimization can delay or hide pushes |
| Access to your claude.ai account's email | A searchable record of every run | Filters and spam folders; easy to ignore | |
| Slack | Slack available to your Claude account (connect it if the option is unavailable) | Seeing results where you already work | Goes to you, not your team |
- Critical checks (alerts, failed deploys): push plus Slack.
- Daily or weekly reports: email or Slack, so you can read them when you sit down.
- Long-running jobs started on demand: push, so you know when to review the result.
Setting up push: install the Claude app for iOS or Android, sign in with the same claude.ai account and organization, and accept the notification permission prompt. Run /mobile in Claude Code to get a QR code for the app.
How the one-line summary works
When a run completes, Claude writes a one-line summary of what happened and sends it to the channels you checked. Tasks fall into two groups:
- Tasks that do work (reports, reviews, cleanups): you get a summary after each run.
- Tasks that watch for a condition (an error spike, a new issue, a price change): you are only notified when there is something worth telling you, so a quiet check stays quiet.
The summary describes the run, and the run is only as clear as its prompt. Open the run from the task's History to see the full session.
Write prompts that make good notifications
For a watch task, say what counts as worth reporting and what a quiet run looks like:
Check the status page and the error dashboard for the checkout service.
Only report when something needs attention:
- If error rate is above 1% or any incident is open, end your run with one
line: "ALERT: <what is wrong> - <link>".
- If everything is normal, end with exactly: "No issues found."
Do not open pull requests or change anything. This is a read-only check.
For a report, put the detail somewhere durable and end with one line that fits a phone screen:
Every Monday, summarize last week's merged pull requests in api-server.
Write the full summary to a pull request comment on the weekly-notes
tracking issue.
End your run with one line I can read on my phone, in this format:
"Weekly notes: <N> PRs merged, <M> need docs, <link to the comment>"
- Lead with the outcome: “3 PRs need docs” beats “Run complete.”
- Include a link to the pull request, issue, or comment with the details.
- Define “nothing to report” so quiet runs do not ping you.
- Avoid sensitive data in the summary; notifications show on lock screens and in inboxes.
More on writing agent instructions: how to build your first AI agent.
Notifying your team, not just you
Scheduled tasks belong to your own claude.ai account, and the built-in notifications go to you. To keep a team informed, have the task post the result where the team looks:
- A Slack channel: include the Slack connector and tell the prompt which channel to post in. Connector actions use your linked account, so the message appears from you; Slack does not usually notify you about your own messages, so keep the built-in notification on for yourself.
- A pull request or issue: the people watching the repository get GitHub's normal notifications.
- An automation: post to a Webhooks by Zapier or Make webhook that routes to Teams, email lists, or a ticket.
For channel design and avoiding alert fatigue, see Slack notification best practices and sending a daily digest instead of many notifications.
Other ways to get notified
| Option | How it works | Use when |
|---|---|---|
| Built-in Notifications tab | Toggle on, pick push, email, and/or Slack | You want a personal heads-up about each run |
| Slack or email connector in the prompt | The prompt tells Claude to post a message or send an email during the run | The team, a channel, or a customer-facing inbox should see the result |
| Webhook to Zapier, Make, or n8n | The prompt calls a webhook URL your environment's network allows; the automation routes it | You want Microsoft Teams, SMS, a ticket, or a table row |
| GitHub notifications | The task opens or comments on a pull request or issue | Code work, where the PR is the real output |
| Task history | Open the task page and read History | Auditing and troubleshooting, not alerting |
For webhooks, the task's cloud environment must allow the webhook's host in its network settings, and the URL should be stored as a network secret or environment variable, not in the prompt. See what a webhook is and connecting Claude Code with Zapier, Make, or n8n.
Notifications for local Claude Code sessions
- Remote Control sessions: run
/configand turn on Push when Claude decides (finished work and other proactive alerts) and/or Push when actions required (permission prompts and questions). You can also ask in your prompt: “notify me when the tests finish.” - Desktop scheduled tasks: run on your computer while the app is open and the computer is awake; Desktop shows a notification when a catch-up run starts after missed runs.
- Terminal: a terminal bell or hooks can alert you when a local session finishes.
Cloud scheduled tasks keep running with your computer off, which is why their notifications come through the app, email, and Slack.
Test your notifications
- Turn on notifications and check every channel you plan to use.
- Click Run now on the task page.
- Confirm the push, email, and Slack message arrive, and that the summary is useful.
- For a watch task, run it once when nothing is wrong (expect silence) and once with a test condition (expect a notification).
- Uncheck the channels you do not need.
Notifications are part of monitoring, not all of it; see how to test and monitor AI agents.
Troubleshooting
| Problem | Check |
|---|---|
| No push on your phone | The app is installed and signed in to the same account and organization; OS notifications are allowed for Claude; on iOS, Focus and summaries; on Android, battery optimization and the app's notification categories |
| Push stopped arriving on Android | At the time of writing, users reported scheduled-task pushes not arriving on Android in a public GitHub issue; use email or Slack as a backup until it is resolved |
| No email | Spam and filters; the email on your claude.ai account |
| No Slack message | Whether Slack is connected to your Claude account and which workspace it uses |
| Nothing on a watch-type task | The run may have found nothing worth reporting; open History to confirm the run happened |
| Summary is vague | Give the prompt an exact last-line format |
| No notification, but the run is still open | The run may be waiting on a permission prompt; open it from History and answer |
| Too many notifications | Report only on change, run less often, or send a digest |
For API-started runs, the caller also gets a session link right away; see how to trigger Claude Code agents via API.
Tracking ChatGPT agents too? See how to monitor workspace agent runs by tracking run status.
Frequently asked questions
How do I get notified when a Claude Code scheduled task finishes?
Open the task, choose Edit, expand Advanced settings, open the Notifications tab, turn on Notify me when this scheduled task finishes, and check Push notification, Email, Slack, or any combination. Claude sends a one-line summary when each run completes.
Can Claude Code routines send Slack notifications?
Yes. Check Slack on the task’s Notifications tab to get a summary of each run in Slack. To post to a team channel instead, include the Slack connector and tell the prompt which channel to post in.
How do I get push notifications for Claude Code scheduled tasks?
Install the Claude app for iOS or Android, sign in with the same claude.ai account, allow notifications, and check Push notification on the task’s Notifications tab. Check Focus modes on iOS and battery optimization on Android if pushes are delayed.
Why didn’t I get a notification for my Claude Code scheduled task?
For tasks that watch for a condition, Claude only notifies you when there is something worth telling you. Otherwise check that the run happened in History, whether it is waiting on a permission prompt, your phone’s notification settings, and email filters. Some users reported Android pushes not arriving at the time of writing, so add email or Slack as a backup.
How do I make Claude Code scheduled task notifications more useful?
End the prompt with an exact one-line format that leads with the outcome and includes a link, define what counts as nothing to report for watch tasks, and keep sensitive data out of the summary.
Disclaimer: Claude Code scheduled tasks (formerly routines) and their API are in research preview, and agent platforms, endpoints, limits, and features change quickly; details reflect public documentation and coverage at the time of writing, so confirm current details with each provider before building. Automation Ace is not affiliated with the companies named here. This article may include links to apps, products, or services; some links may be affiliate links, which means Automation Ace may earn a commission at no extra cost to you.