An automation that silently does work has no audience. Adding a Slack post or email turns it into a daily ritual. Good notifications: - One message per run - Includes a one-sentence summary - Has a link to the full output - Calls out exceptions / errors - Doesn't spam Make notifications first-class. They're how the human in the loop stays in the loop.
Easiest: incoming webhook URL. 1. Slack → Apps → Incoming Webhooks → Add to a channel 2. Copy the URL (treat as secret; put in env var) 3. POST JSON to it from your script For richer messages, use Block Kit (markdown-ish blocks) — formatted summaries, action buttons, dividers. For interactive bots (responding to commands), step up to Bolt SDK or Slack's events API. 90% of automations need just the webhook.
POST JSON to the webhook. Block Kit for nice formatting. One reusable function for every script.
smtplib works for simple emails. For anything user-visible (alerts, reports, password resets) use Postmark or Resend: - Better deliverability (won't end up in spam) - Templates with HTML + plaintext - Open / bounce tracking - Reasonable free tiers Don't use Gmail SMTP for production email — it's rate-limited and Gmail will throttle you. Free tier of Postmark / Resend covers most personal automations.
Day 81 done. - Notifications close the automation loop - Slack webhooks for 90% of cases - 10-line notifier - Postmark / Resend for email Tomorrow (Day 82): PDF and Excel automation. The unsexy stuff that pays bills.