Scheduled Tasks
Write a task in plain English
A scheduled task has four parts:
- A name — something memorable, like Morning Brief or Weekly Pipeline
- An instruction — a sentence or two telling Deck what to do
- A schedule — when (and how often) it should run
- Integrations — the tools Deck can read from when the task runs (calendar, inbox, CRM, meeting notes)
That's it. You can change any of them later, or pause the task entirely.
Step by step
- Open Scheduled Tasks and click New task.
- Give it a name.
- Write the instruction in plain English. Examples:
- "Summarize every project updated this week with status and next steps."
- "Pull overnight news mentions for the companies I'm tracking and flag anything material."
- "The day before any renewal call in HubSpot, send me a one-line reminder with the account and the renewal date."
- Pick a schedule — see Schedules for the options.
- Send a test run to yourself to confirm the output looks right before letting it fire on schedule.
- Save. The task fires at the next scheduled time.
Reference your projects, integrations, and playbooks
You can name specific projects, integrations, or playbooks inside a task instruction — "each Monday, run the Pipeline-Review playbook against my Acme Renewal project and HubSpot pipeline". Doing this turns a routine into a small custom skill that knows where to look and how to behave.
If you find yourself writing the same multi-step instruction across several tasks, lift the steps into a playbook file once and reference it by name in each task. For inspiration on what skill-like instructions can do, browse the Anthropic Claude Skills repo.
Tips for good instructions
- Be specific about the result. "Three bullet points" is better than "a summary."
- Reference what Deck already knows about you — your projects, contacts, and integrations.
- Tell Deck what to skip. If you only care about active deals, say so.
Vague vs. specific
| Vague | Specific |
|---|---|
| "Send me a daily news summary." | "Each weekday at 7 AM, send three bullets on overnight news that mentions any company in my active projects. Skip macro headlines unless they name a company I'm tracking." |
| "Tell me about my projects." | "Every Monday at 9 AM, list each project updated in the last 7 days with its status, the most recent document added, and one suggested next step." |
| "Remind me about Acme." | "The day before the Acme contract expires, email me a one-line reminder with the renewal date and a link to the Acme project." |
The pattern: name the when, the format, the what to cover, and one example if the request could be read more than one way.
Connect integrations to power your tasks
Tasks get sharper when Deck can read from the tools you already use. Connect once and any task can pull from them:
- Calendar and inbox — "List who I'm meeting today" needs Google or Microsoft.
- CRM context — "Flag deals that haven't moved in two weeks" uses HubSpot.
- Meeting notes — "Recap yesterday's Acme call" reads from Fireflies or Granola.
- Team knowledge — "Cross-check this against our positioning" pulls from Notion.
See the full list and connect what you need on the Integrations page.
Editing and pausing
You can pause, edit, or delete any task from Scheduled Tasks. Pausing keeps the task in place but stops it from firing — useful when you're on holiday.
Read next
- Schedules — pick the cadence that fits the work.
- Run on demand — trigger a task before the next scheduled fire.