Controlling notifications for a scheduled workflow
A scheduled workflow runs on its own, so a notification is how you find out it has produced something. Because a daily schedule and a monthly one deserve different treatment, you set these notifications on each schedule rather than once for your whole account.
When you are notified
You are notified once per run, at the moment the run stops and produces its first response. The notification tells you which of three things happened:
| State | What it means | What to do |
|---|---|---|
| Result ready | The workflow finished the work you asked for. | Open the run and read the response. |
| Input required | The workflow cannot go further without an answer from you. The notification is marked Action required. | Open the run and reply. You will not be chased again. |
| Could not complete | The run stopped because of an error. | Open the run to see what failed, then retry or adjust the workflow. |
You are not notified when a run starts, and you are not notified a second time after you respond to a run that asked for input. Opening the notification takes you to the workflow chat for that run.
Who receives these notifications
Only the owner of the schedule — the person who set it up. Other members of the workspace are not notified when your schedule runs.
Turning them on or off
Open the workflow's ⋮ menu on the Workflows page and choose Set Schedule. Below the Schedule Enabled toggle you will find two tick boxes:
- Notify me in the app — shows an in-app notification when a scheduled run of this workflow produces its first response.
- Notify me by email — emails you when a scheduled run of this workflow produces its first response.
Both are ticked by default. Clear either one to stop that channel for this schedule alone; every other schedule keeps its own settings. Unlike your profile notification settings, these do not save on click — select Save Changes before closing the dialog.
This is the only place scheduled-run notifications are configured. They do not appear in the Notification preferences card in your settings, so there is no global switch that can conflict with what you set here.
What stays switched on
Turning off notifications for a schedule silences the run itself, not the work it produces. If a run assigns an Action to you, you are still notified about that Action, because it is a separate event with its own settings.