By 8am, yesterday's daily report is already in Slack
Start from a template, write not a line of code, and hand the daily grind of pulling data, organizing, and reporting to a workflow. Steps that need a human call pause and wait for your approval; the rest of the time it runs on its own.
07:58:02 fetch_ad_spend ok asa + google_ads 07:58:41 fetch_subscriptions ok window: yesterday 07:59:10 build_xlsx_report ok dod / wow / mom 07:59:36 ai_commentary ok attached to report 08:00:00 deliver_slack ok #growth-daily
A no-code path
From picking a template to receiving your first report, not a single step requires writing code; to change the process, just say a sentence to the AI assistant.
Four things operations teams do with it every day
All from workflows actually running in production. Each card is labeled with its trigger and where a person is involved.
- The production template has iterated to v2.0.74
- Data, table, and commentary are all in the channel—no need to log into a backend
- Na rejeição ou tempo limite, zero mudanças na produção
- Bid changes are clamped so they can't jump to an absurd value in one step
- Negative-review alerts are pushed instantly, not held for the daily report
- Drafts never go live on their own—human review is required before publishing
- There's a Webhook-triggered variant to wire into your own systems
- Want a quick look? Kick off a manual run anytime
Se falhar às 3 da manhã, retoma de manhã
The biggest worry with scheduled reports is a silent failure overnight. The execution engine auto-resumes unfinished executions after a service restart, so what you see in the morning is still a complete report.
- Auto-resume continues from the last unfinished step; before recovering, the workflow definition's SHA-256 hash is verified, and the number of resumes is capped
- Read-only and pure-computation steps can be marked idempotent, so replaying them on resume is safe; completed steps won't run again, and the report won't be sent twice
- Every step's logs, duration, and cost stay in the execution history; a failure can rerun from a specified step, with completed AI steps not billed again
02:14:07 fetch_ad_spend ok 02:14:52 build_xlsx_report interrupted · restart 02:16:33 auto_resume sha-256 verified 02:16:34 build_xlsx_report resumed 02:17:41 ai_commentary ok 02:18:02 deliver_slack ok #growth-daily
The things that need your call, gathered in one inbox
Any step in a workflow can require human approval: the AI only produces suggestions, and nothing executes until you approve.
- To-dos gather in the approval inbox, with notifications going through three channels at once—in-app, email, and API
- Values in the approval form can be edited inline: change the suggested bid to the number you want, then click Approve
- Auto-reject on timeout with a configurable duration; neither rejection nor timeout touches anything in production