Ops

Weekly customer health reports that write themselves

Every Monday, pull usage, tickets and billing for each key account, write a short health summary and send it to the account owner.

Trigger

cron 0 7 * * MON

Stack

warehouse · crm · llm · docs · mail

Result

42 account reports every Monday at 7:00

6 steps in this workflow

Weekly customer health reports that write themselves: workflow diagram drawn in characters

The problem

Account managers want a weekly read on their customers, but nobody wants to maintain the spreadsheet that produces it.

How the workflow runs

A cron trigger fans out one child run per account with step.invoke. Each child queries the warehouse, pulls open tickets and the latest invoice, then asks an LLM to write four sentences: what changed, what’s at risk, and one suggested action.

Reports land in a shared doc and in each owner’s inbox. If the warehouse query times out for one account, only that account retries; the other 41 are already sent.

What changes

Health reviews start from the same facts every week, and the prompt that writes them lives in version control with the rest of the code.

Get started

Ship the agent. Keep the receipts.

Free for 50,000 steps a month. No credit card, no separate workers, and your first durable workflow deployed before lunch.

orrindel

Durable runtime for AI agents and automations. Every run, in plain text.

Book a 20-minute demo →
All systems normal
99.99% uptime · last 90 days
90 days agotoday
regions us-east · eu-west · ap-south
soc 2 type ii · gdpr · hipaa (baa)
sdk v4.2.1 · node · python · go
© 2026 Orrindel Labs, Inc.PrivacyTermsSecurityMade in plain text.

Create a free website with Framer, the website builder loved by startups, designers and agencies.