Skip to content
Dash
Get started for free Get started for free

Schedule a task

A scheduled task is something Dash does without you asking each time. You describe the work, pick a schedule, and tell Dash where to send the result, all inside the task’s instructions.

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

Create a scheduled task

Section titled “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 [email protected].

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

Section titled “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

Section titled “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

Section titled “Delivery”

Delivery is part of the task’s instructions. You tell Dash where to send results the same way you’d tell a colleague: name the channel, the DM, or the email address right in the instructions.

Every run’s result also appears in the Dash web app automatically, so you can always review what happened even if the task doesn’t post anywhere else.

Examples of delivery in instructions:

@Dash every weekday at 8 AM, pull the pipeline snapshot from HubSpot and post a summary to #sales.

@Dash on the first of every month, email a churn report to [email protected].

@Dash every Monday at 9 AM, pull the sprint digest and DM me the result.

Because delivery lives in the instructions, you have full control. A task can post to a Slack channel, a Teams channel, send a DM, email one or more recipients, or text you via SMS, all in one run.

Silent tasks

Section titled “Silent tasks”

Sometimes you want a task to run on schedule but stay quiet unless there is something to report. For example, a daily overdue-ticket check that only pings the channel when it finds one, or a compliance scan that stays silent when everything passes.

Tell Dash the condition directly in the instructions:

@Dash every morning at 9 AM, check the support queue for tickets older than 48 hours. Only post to #support-alerts if there are any.

@Dash run a daily invoice audit. Stay silent if everything looks good; DM me if anything is flagged.

Dash follows the condition: it only sends when the instructions say to. Every run still appears in the Dash web app, so you can always review what happened, but your channel or inbox stays clear when there is nothing to act on.

Manage scheduled tasks

Section titled “Manage scheduled tasks”

From Slack or Teams

Section titled “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

Section titled “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 approvals settings. You can also pause, resume, or delete tasks from here.

Run a task immediately

Section titled “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.

Approvals

Section titled “Approvals”

When a task runs without autonomous mode, Dash pauses at any action that needs approval and sends an approval card. You can choose where that card goes:

  • A Slack or Teams channel — set the channel in the Approvals section of the task form on the web dashboard. The approval card appears in that channel so the team can act on it.
  • The task creator’s DM — leave the approvals channel blank, and Dash sends the card directly to you.
  • Email — if no chat surface is connected, Dash falls back to an email notification.

You approve or deny from the notification, and the run completes.

Only workspace admins can enable autonomous mode. When autonomous mode is on, the task runs without pausing for approval. The task detail view shows who enabled it. If that person’s admin role has changed since they granted autonomy, Dash suspends autonomous mode and runs pause for approval again until an active admin re-enables it.

Who can manage a task

Section titled “Who can manage a task”

By default, only the person who created a scheduled task or a workspace admin can edit, pause, resume, run, or delete it. Other team members can see the task on the Scheduled Tasks page, but the controls are locked. The task detail shows “Created by [name]” so you know who owns it.

Share access with specific people

Section titled “Share access with specific people”

The task creator, a workspace admin, or anyone already on the list can add other team members to a task’s Permissions list, giving them the same management abilities: edit, pause, resume, run, delete, and change who has access. Open the task on the Scheduled Tasks page and go to the Permissions tab to add or remove people.

People on the Permissions list can manage the task the same way the creator can, but the task still runs as its creator. Adding someone to the list does not change whose tool connections, skills, or identity the task uses at run time.

If you need to change a task you didn’t create and you’re not on its Permissions list, ask the creator, someone with access, or a workspace admin.

How scheduled tasks use your tools

Section titled “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.

When a run can’t start

Section titled “When a run can’t start”

If a scheduled run can’t fire, Dash tells the person who can fix it:

  • Browser task without Chrome — Dash notifies the task creator. 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 — Dash notifies the workspace admins, since only an admin can add credits. Once credits are added, the next scheduled run will go ahead.

If the previous run is still going when the next one is due, Dash skips the new run quietly. Nothing needs fixing.

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

What’s next

Section titled “What’s next”