Schedule a task

A scheduled task is something Dash does without you asking each time. You describe the work, pick a schedule, and Dash runs it on its own, posting the result to a Slack channel, a Microsoft Teams channel, a DM, or an email address.

Morning briefings, weekly pipeline snapshots, daily support digests, end-of-month reports, all of these are scheduled tasks.

Create a scheduled task

Tell Dash what you want, when you want it, and where to deliver it:

@Dash every weekday at 8 AM Eastern, pull MRR from Stripe and pipeline from HubSpot, and DM me a one-page summary.

@Dash every Monday at 9 AM, post a sprint digest to #engineering.

@Dash on the first of every month, email a churn report to leadership@example.com.

Dash will read back the task, confirm the schedule and delivery destination, and offer a test run before scheduling. Always test-run first to catch any formatting or data-source issues.

One-time tasks

Not everything needs to repeat. You can schedule a single future run:

@Dash tomorrow at 3 PM, pull the latest ad spend numbers and post them to #growth.

@Dash on August 15 at 9 AM, send a renewal reminder email to the Acme team.

The task runs once and doesn’t recur.

Schedules

Dash supports natural-language schedules that it converts to cron under the hood:

• Every weekday at 8 AM — Monday through Friday.
• Every Monday at 9 AM — weekly on a specific day.
• Every 6 hours — throughout the day.
• First of every month — monthly.
• Every Friday at 4 PM — end-of-week reports.

All times are in the timezone you specify (or the workspace’s default timezone if you don’t). You can change the timezone per task.

Delivery

Every task’s result appears in the Dash web app automatically. This is the always-on destination: you can always find the run in your Dash chat in the web app, even if you don’t add any other delivery channel.

To also deliver results (and approval requests) to a chat channel or email, add one or more destinations:

• Slack channel — Dash posts to a channel. The first run requires your approval (since it’s a public action). After that, subsequent runs go through automatically.
• Microsoft Teams channel — on a Teams workspace, Dash delivers the result to a Teams channel the same way it does to a Slack channel.
• Email — Dash sends the result to one or more email addresses.

You can set multiple destinations on the same task. Adding a Slack or Teams channel is recommended: approval cards for that task will appear in the channel, so you don’t miss a parked run. Without a delivery channel, a parked approval is sent only to the task owner.

When you create a task from a Slack or Teams channel and don’t specify a delivery channel, Dash automatically adds that channel as a delivery target. This way, results and any approval cards land where the conversation started instead of only in a DM.

Manage scheduled tasks

From Slack or Teams

@Dash show my scheduled tasks

@Dash pause the morning briefing

@Dash change the sprint digest to 10 AM instead of 9 AM

@Dash delete the monthly churn report

From the web dashboard

Go to app.dashpup.ai and open the Scheduled Tasks page. Tasks are split into two tabs: Current (active and paused tasks) and Past (completed, archived, and deleted). Use the search bar to find a task by name, or filter by lifecycle status.

Each task shows its schedule in natural language, its next run time (if active), and status chips: Autonomous for unattended tasks, Autonomy paused when the granting admin’s role changed, and Failed if the last run didn’t succeed. Click a task to edit its instructions, schedule, or delivery. You can also pause, resume, or delete tasks from here.

If a task runs in autonomous mode, the detail view shows who enabled it. If that person’s admin role has changed since they granted autonomy, Dash suspends autonomous mode and an amber warning explains why. Runs will pause for approval again until an active admin re-enables autonomy.

Run a task immediately

You can trigger any scheduled task on demand without waiting for its next run:

@Dash run the morning briefing now

This fires a single run immediately. It doesn’t affect the regular schedule.

How scheduled tasks use your tools

A scheduled task runs headlessly, meaning there’s no open conversation. Dash uses the same tool connections, skills, and memory it would in a normal chat. The task’s instructions are self-contained, so Dash doesn’t need to see prior conversation context.

If a task needs a tool that requires approval, Dash will hold the run and notify you. When the task has a delivery channel, the approval card appears there. When it doesn’t, Dash sends the card as a DM to the task owner on Slack or Teams, so you can approve or deny without switching context. If neither channel is available, Dash falls back to an email notification. You approve or deny from the notification, and the run completes.

When a run can’t start

If a scheduled run can’t fire, Dash posts a notice to the task’s delivery channel explaining what happened:

• Browser task without Chrome — the task runs in the browser, so it needs Chrome open on your computer with the Dash extension signed in. Nothing ran; the next scheduled run will try again.
• Out of credits — the workspace’s credit balance is empty. Add credits and the next scheduled run will go ahead.

Skipped runs also appear in the Activity feed so admins can spot recurring issues.

What’s next

• Ask Dash for a report to learn how to get the best results from data pulls, whether scheduled or on-demand.
• Install and use skills to teach Dash reusable playbooks it can follow on a schedule.