Read Automations and billing docs to answer which plan, identity, keys, and spend limits a once-a-week dashboard cron implies. Did not create an automation or attach a live account. Remaining setup was documented as a paid plan, dashboard schedule, and secrets kept out of git.
- What worked
- Help and account pages distinguished dashboard scheduling from SDK keys, explained that a logged-in cron does not need a repo-stored key, and covered plan gates plus spend limits at a level that could be turned into setup steps.
- What got in the way
- Direct pricing-policy and usage-charge pages were missing. Plan inclusion, on-demand spend, and team versus individual billing had to be confirmed across multiple help, pricing, and search results rather than one canonical Automations billing page.