Skip to main content

Documentation Index

Fetch the complete documentation index at: https://adapt.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

Schedule any Adapt query to run automatically — on a recurring cadence, or once at a specific future time. Each execution runs in a fresh chat with your integration access, and results land wherever you want them: a Slack DM, a Slack channel, or the web app. If you find yourself asking the same question every Monday morning, stop doing that.

How it works

Describe the task in plain English — the same way you’d ask it manually. Adapt parses the schedule, confirms it back to you, and starts running it on its own.
Every Monday at 9am, summarize last week's closed deals
and post it to #sales.
Every morning at 8am, pull any new critical errors from Sentry
and DM them to me.
On the first of every month, generate a revenue report
and share it as a new chat.
Each execution starts a brand-new chat. The task has no memory of prior runs — if you want it to compare against last week, say so in the prompt, and Adapt will pull the prior data itself.

Schedule types

Recurring tasks

Daily, weekly, monthly, or any custom cadence. Describe it in plain language or use a cron expression.
Every weekday at 9am, list PRs that need review and any blocked issues.
Every other Wednesday at 2pm, draft a sprint retro from #engineering.

One-time tasks

Schedule something to run once at a specific future moment:
In 3 hours, check if the deploy finished and summarize any new errors.
Tomorrow at 7am, summarize what happened in #incidents overnight.

Cron expressions

For precise control, Adapt accepts standard 5-field cron expressions (minute hour day month weekday). The minimum interval between recurring runs is 15 minutes.
ExpressionRuns
0 9 * * *Every day at 9:00 AM
0 9 * * 1Every Monday at 9:00 AM
0 9 * * 1-5Weekdays at 9:00 AM
*/30 * * * *Every 30 minutes
0 */4 * * *Every 4 hours, on the hour
0 0 1 * *First day of each month at midnight
Times are interpreted in your account’s timezone.

Delivery options

Choose where results land:
  • Slack DM — Direct message from the Adapt bot
  • Slack channel — Post to a specific channel (name the channel in your prompt)
  • New chat — Results appear as a new conversation in the web app
If you don’t specify a destination, results post wherever you scheduled the task from. Tasks scheduled inside a Slack thread will reply in that thread by default; tasks scheduled in the web app create a new chat.

Visibility

Each task is either private or shared:
  • Private — Only you can see the chats the task creates. Useful for personal reminders, inbox triage, or anything tied to your own credentials.
  • Shared — Chats created by the task are visible to your whole organization. Useful for team standups, exec reports, or any task whose output the team should be able to read, fork, and follow up on.
Tasks inherit the visibility of the chat you scheduled them from. To change it, just ask:
Make my Monday sales summary shared with the team.

Permissions

Scheduled tasks run with the same integration permissions as your account at the moment they execute. If you disconnect HubSpot or lose access to a Slack channel, any task that depends on it will fail or skip that step on its next run. For tasks the whole team relies on, schedule them from an account whose integration access is unlikely to change.

Managing your tasks

View your tasks

What recurring tasks do I have running?
Show me every scheduled task in the org.
You can also browse and manage all of your scheduled tasks in Settings → Scheduled Tasks in the web app.

Edit a task

Tasks aren’t write-once — change the schedule, the prompt, or the delivery target at any time:
Change the Monday sales summary to run at 8am instead of 9am.
Update the daily Sentry digest to also include any new bugs filed in Linear.
Have my weekly engineering summary post to #eng-leads instead of DMing me.

Pause or cancel

Pause the Monday sales summary for the next two weeks.
Cancel the daily Slack report.

Pairing with skills and proactive Slack

Scheduled tasks become much more powerful when combined with the rest of the platform:
  • Skills define how a recurring task should be done — the playbook, the data sources, the format. Scheduling a task that says “run the weekly-engaged-leads-by-source report and post it to #marketing” gives you a consistent, repeatable deliverable instead of a one-off summary that drifts in shape week over week.
  • Proactive Slack mode decides when Adapt should jump in based on what’s happening in a channel. Scheduled tasks decide when Adapt should jump in based on the clock. They compose well: a daily 9am rollup of overnight incidents, plus a proactive policy in #incidents that wakes Adapt up the moment a new one lands.

Example use cases

Engineering

Every weekday at 9am, list open PRs older than 48 hours
and any P0/P1 bugs filed in Linear since yesterday.

Sales

Every Monday at 8am, summarize deals that moved stage last week,
deals that went quiet for 7+ days, and any new opportunities
created in HubSpot. Post it to #sales-leadership.

Customer success

Every Friday at 4pm, pull the week's new support tickets from Zendesk,
group them by theme, and flag any account that filed more than 3.

Competitive monitoring

Every day at 7am, search the web for news about [competitor]
and DM me anything substantive.

Exec reporting

On the first business day of every month, assemble a one-page
executive summary from finance, product, and sales data.
Share it as a new chat.

Limits

  • Minimum recurring interval: 15 minutes
  • One-time delay window: 60 seconds to 7 days in the future
  • Cron format: Standard 5-field expressions (minute, hour, day, month, weekday)
  • Permissions: Tasks run with your account’s integration access at execution time

Next steps

Slack App

Receive scheduled task output in Slack

Skills

Turn one-off prompts into repeatable playbooks

Ask Questions

Learn how to query your data

Integrations

Connect data sources for richer scheduled output