Email me a weekly summary
Every Monday morning, gather last week and email you a short summary when there were numbers worth sending.
What it does, step by step
- Read last week's numbers from the metrics service.
-
Decide whether there were any numbers worth sending.
- yes goes to "Email the summary"
- no goes to "Stay quiet"
- Send the short weekly summary by email.
- Nothing worth sending this week, so send nothing.
Build it just by talking to Claude
You do not wire this by hand. You describe it in a sentence, your Claude builds it, and Autoploy keeps it running.
What to build: Email me a weekly summary. Every Monday morning, gather last week and email you a short summary when there were numbers worth sending. This is for founders and non-technical builders. How it behaves: 1. Runs every Monday at 08:00 UTC. 2. Read last week's numbers from the metrics service. 3. If any numbers this week, then go to "Email the summary", otherwise go to "Stay quiet". 4. Send the short weekly summary by email. 5. Nothing worth sending this week, so send nothing. The tools: - Resend (for "Which email service should send the summary?"). I will need you to create the key RESEND_API_KEY (Resend API key). I add the values in Autoploy myself; you only need their names. The platform: Connect to my Autoploy MCP server, call get_authoring_guide to read the authoring guide, and build the automation with the Autoploy SDK contract. Model every yes/no fork as a condition step with truthful labeled branches, keep every external side effect idempotent and keyed, and deploy it with deploy_automation. Before you build: Repeat the plan back to me in plain English and ask follow-up questions about anything unclear or ambiguous. Do not guess. Ask me for each key by name when it is time, and never ask me to paste a key anywhere except my own secure setup.
7-day free trial on every plan. You pick your plan at signup, and nothing is charged before day 7.