Scheduled tasks

A scheduled task is a standing instruction you set up once, and Monad runs it automatically on a schedule — as you, using the apps you've connected, and sends any posted result privately to your direct message with Monad. No one else sees it. A task may also complete successfully without posting when there is no useful update or its instruction does not call for a message.

For example:

• “Every morning, check my email and give me the top five things I need to respond to.”
• “Every weekday at 5pm, draft replies to anything in my inbox flagged urgent.”
• “Every Monday, summarize what changed in my projects last week.”

How it runs#

A scheduled task runs on your behalf: it sees what you can see and uses the integrations you've connected (like your email or calendar). When it posts, it delivers privately — never to a channel. Only you can create, pause, or delete your own scheduled tasks.

Two ways to set one up#

• Just ask Monad. In your direct message with Monad, say what you want and how often — for example, “every morning, check my email and give me the top five things to respond to.” Monad will set it up and confirm.
• From settings. Go to Settings → Account → Scheduled tasks, choose New task, and fill in a name, the instruction, when it should run, and your timezone.

Managing your tasks#

In Settings → Account → Scheduled tasks you can see each task, when it last ran, whether that run posted a result or completed silently, and:

• Run now — try it immediately; any posted result appears in your DM.
• Pause / Resume — temporarily stop a task without deleting it.
• Delete — remove a task for good.

Good to know#

• Tasks run at the time you set, in your timezone. Automatic daylight-saving adjustment is coming soon — until then, a task may run an hour off for part of the year, and you can update it if needed.
• A task can run at most every 15 minutes.
• If a task runs through an automation role, changing that role's instructions, tools, model, limits, enabled state, or retirement status automatically pauses the task. Review the role, then choose Resume to explicitly approve the updated profile.
• If the role is disabled, re-enable it before resuming the task. If the role was retired, delete the task and create a new one with an available role.
• A successful run that intentionally sends no message appears in run history as Completed without posting. This is a successful outcome, not a hidden failure.
• If an app a task needs (like your email) isn't connected or its access has expired, Monad will DM you to reconnect it instead of failing silently.
• A scheduled task needs your connected apps, so Monad always runs it as you — that's how it can actually reach your email, calendar, and other integrations. It won't quietly set up a task that can't see your apps and then come up empty.
• Scheduled tasks are different from Monad's automatic check-ins: a check-in is Monad keeping an eye on things on its own; a scheduled task is a specific instruction you wrote, on a cadence you chose.