Where I write
Your account email, extra addresses, Slack, Discord and your own endpoint — and why each one confirms itself before I use it.
Your account email is already one
You never have to set anything up to be told. The address you signed in with is where I write, and it does not count towards your plan's number of destinations. The moment you add and confirm another email address, I use that one instead.
One message is about your account rather than about a project, and it always goes to the address you signed in with: if you move to a smaller plan and end up with more projects than the plan covers, I write once to say so and list the plans, and then not again unless it happens again.
The oldest projects stay covered first. Within each covered project, the active checks you added first stay covered first too. Newer projects and checks above the limits stay saved but paused by the plan. Archive a project, turn off a check, or pick a bigger plan to change what fits. Nothing is deleted, archived, or turned off automatically.
Adding somewhere else
In your settings, under Where should I write?, you can add an email address, a Slack or Discord channel, or your own endpoint. How many you may have at once depends on your plan — see pricing.
For Slack and Discord, paste the incoming webhook URL that the channel gave you. I accept those two hosts only, matched exactly, because a URL that merely looks like Slack is a URL pointing somewhere else.
Every destination confirms itself first
The moment you add one, I send a single message to it carrying a confirmation link and nothing else — no project name, no address, no check. Someone has to open that link and answer Yes, write here. Until they do, I write nothing there at all.
This is not ceremony. Anyone can type an address they do not own into a form; the round trip is what proves the place I am about to write to actually wanted to hear from me. It is also why the link needs a real click: link scanners in mail systems open every URL they are sent, so opening it is deliberately not enough on its own.
For an endpoint of your own, the confirmation link arrives in the body of a request rather than in an inbox — your own webhook shows what that request looks like and where to find the link in it.
If the link stops working
A confirmation link is good for 24 hours and can be used once. If you missed it, press Send again next to the destination in your settings. That sends a fresh link and stops the old one working — so you never have to remove the destination and add it back, which for an endpoint would issue a new signing secret and mean redeploying your receiver.
You can do that a few times a day per destination, counted for that destination across every account on this product. It is the ceiling on how much post can reach somebody who never asked for any, so it applies to the first message and to every one after it.
Removing one
Remove takes effect immediately and needs no confirmation of its own. If the one you removed was your only confirmed email address, I go back to writing to your account email — you are never left with nowhere to be told.