Post a daily summary to Slack
Every weekday morning, summarize yesterday and post the digest to Slack when there is something to report.
What it does, step by step
- Read yesterday's events from the metrics service.
-
Decide whether there was any activity worth sending.
- yes goes to "Post to Slack"
- no goes to "Stay quiet"
- Send the digest to the team channel.
- Nothing happened yesterday, 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: Post a daily summary to your team chat. Every weekday morning, summarize yesterday and post the digest to your team chat when there is something to report. This is for engineers and non-technical builders alike. How it behaves: 1. Runs every weekday at 09:00 UTC. 2. Read yesterday's events from the metrics service. 3. If anything to report, then go to "Post to Slack", otherwise go to "Stay quiet". 4. Send the digest to the team channel. 5. Nothing happened yesterday, so send nothing. The tools: - Slack (for "Where should the daily digest be posted?"). I will need you to create the key SLACK_BOT_TOKEN (Slack bot token), provide the setting SLACK_CHANNEL (Slack channel). 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.