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 with a free JSON API that any automation platform can read, plus optional private inboxes, push notifications and a capture-only send side for testing.

trigger (schedule or event) → HTTP GET /api/inbox → branch on subject / sender → act: extract code, forward, store

Poll from anything that speaks HTTPS

The read side is one GET returning JSON — no SDK, no signature verification, no auth for named inboxes:

# cron every minute: react to new mail for a dedicated address
*/1 * * * * curl -s "https://tempx.uk/api/inbox?address=alerts-7cq2@tempx.uk" \
  | 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.

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.

When the inbox should not be public

Named inboxes are public-by-knowledge: anyone who learns the address can read it. For automations that handle anything sensitive, create a private inbox from your account and authenticate reads with its Bearer token — same API, closed door:

curl -s -H "Authorization: Bearer YOUR_PRIVATE_INBOX_TOKEN" \
  https://tempx.uk/api/inbox

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