How do I create a scheduled analysis?
Schedule an analysis to run daily, weekly, or weekdays at a specific time and timezone. Relative date ranges only. Draft, review, activate.
TL;DR
Open /schedules and click New schedule. Draft a configuration
(prompt, filters, relative date range), pick a cadence (daily,
weekly, or weekdays) with a time and timezone, review, then click
Activate. The schedule runs on its cadence until you pause it.
Steps
- 01Open
/schedulesand click New schedule. The builder opens in draft state — no runs fire yet. - 02Configure the analysis the same way you would at
/new: pick a prompt (library or your own), set HubSpot filters, pick a model, pickmax_calls. Use a relative date range (last week, last 30 days, last 7 weekdays). Absolute ranges are blocked for schedules. - 03Pick a cadence. Three options:
- 04Pick a time and a timezone. The schedule fires at that local time every cadence. Daylight Saving is handled — the schedule tracks the wall-clock time, not UTC.
- 05Optionally set a per-schedule Slack webhook (overrides the workspace-level Slack integration for this schedule). See How do I send different schedules to different Slack channels?.
- 06Click Review, confirm the configuration summary, then click Activate. The schedule is live; the next firing time is shown on the schedule card.
Draft → review → activate
Schedules don't fire while in draft state. The three-stage flow exists so you can build, sanity-check, and explicitly turn on a schedule — no accidental "saved and live" runs. To pause an active schedule, click Pause on its card; runs stop until you Resume.
Reports from scheduled runs
Reports generated by a schedule are tagged with triggered_by: "schedule" and the schedule name. Filter for them on /dashboard to
separate scheduled reports from ad-hoc ones. Quota and retention work
exactly the same as ad-hoc runs.
Execution history
Each schedule has an execution history view showing the last N firings — when each ran, whether it succeeded, the resulting report ID, and any quota or filter issues. Useful for diagnosing why a schedule produced zero calls last Tuesday.