Tempx.

Tempx for automation

A mailbox is the most reliable webhook on the internet: nearly every service can send email, far fewer can call your endpoint. Tempx turns that fact into a building block — a disposable inbox any automation platform can read, with a token-authenticated read side, optional private inboxes, push notifications and a capture-only send side for testing.

event triggerread new mailfilter subjectextract & act

Poll from anything that speaks HTTPS

The read side is one authenticated GET returning JSON — no SDK, no signature verification:

# cron every minute: react to new mail in a dedicated private inbox
*/1 * * * * curl -s -H "Authorization: Bearer $TEMPX_TOKEN" \
  https://tempx.uk/api/inbox \
  | jq -e '.messages[] | select(.subject | test("backup failed"))' \
  && notify-oncall

Client-side browser calls are refused by design; anything running server-side (n8n, Make, Zapier, GitHub Actions, a Raspberry Pi) works as-is. Rate limit for reads: 240 requests/minute.

Where the token comes from

Create a private inbox from your account — an unguessable address with 1-hour retention — and pass its Bearer token on every read: same call shape, closed door. Named inboxes are public-by-knowledge (anyone who learns the address can read them), so keep them to throwaway traffic you would happily post on a wall.

The n8n shape of it

In n8n the whole watcher is five nodes: Schedule Trigger (every minute) → HTTP Request to the inbox URL → Filter on subject or from → Code node to extract the interesting part (an OTP, a link, an order number) → whatever acts on it. The full walkthrough with node settings is in the n8n integration.

Humans in the loop, two ways

Give your workflow an address

Pick an inbox, point an HTTP node at it, and stop building webhook receivers for services that only send email.

Open an inbox

Related