Events in. Signals out.
What matters shouldn't stay in another tab.
Automation packs ready to work: guides and step-by-step flows that route your events where you actually act.
From the library
Automations ready to wire up.
What to configure, which secrets you need, and how to test. Each piece is a how-to you can adapt to your stack.
- GitHub Actions → DiscordWhen a CI job fails, an embed lands in your Discord channel.
- Stripe → DiscordIf an invoice payment fails, Discord gets the amount and customer.
- Form → TelegramSomeone submits your form and the alert reaches your chat with name and contact.
- Stripe → TelegramA failed charge reaches your phone on Telegram — no Dashboard tab.
How we think about automations
Three steps.
Whatever the source.
Something important happens
A form comes in, a charge fails, a CI job breaks, or a webhook you already control fires.
It becomes a clear workflow
Steps, conditions and data: a script, a CI workflow or a no-code scenario turns that event into something you can act on.
It lands where you act
CRM, Notion, Discord, Telegram, email — the channel you actually open, without another dashboard in between.
What you get
Not a loose tutorial: the whole flow.
Everything you need to get it running — and everything you need to know it still runs three months from now.
Requirements up front
Which accounts, permissions and access you need before you start. No surprises halfway through.
Reproducible steps
The exact path, in order, with what to copy and where each piece goes.
Secrets handled properly
Where every token lives, and how not to publish it by accident.
A real test
How to fire the event by hand, and what you should see to know it landed.
The usual failures
What actually breaks the first time, and how to get out without starting over.
curl -X POST "$WEBHOOK_URL" \ -H "Content-Type: application/json" \ -d '{"event":"test","source":"local"}'HTTP/2 204
Documentation
Guides to understand it. Automations to build it.
Guides cover the mental model. Automations walk you through the setup step by step. Start with one piece, or jump to the full library indexes.
- GuideStripe webhooks (failed charges)What a Stripe event is, what invoice.payment_failed looks like, and what to check for security before reacting in your own system.
- GuideAlerts with a Telegram botWhat a Telegram bot is, the token, chat_id, and how to test sendMessage before wiring it into your own flows.
- GuideIntroduction to webhooksWhat a webhook is, what an HTTP request looks like, and the minimum security checks before connecting a real emitter.
Contact
If something comes up, write me.
Whether it's a question about a guide, an automation you're wiring up, or a collection you'd like to see. No newsletter involved.
hola@postnaut.com