Rules for arriving mail
written once, run always
Say what happens to a message before anybody opens it.
Rules run as mail arrives. Nothing already in the mailbox moves.
How it works
Running in three steps.
- 01
Write the rule
Conditions on the arriving message, then the actions to take.
- 02
Try it first
Run it over the last thirty days without touching a message.
- 03
Turn it on
It runs on arrival, and the log says what happened.
What it runs on
The parts doing the work.
Nothing here is a separate product. Each one is a piece of the mailbox you already have.
Your own conditions, and what should happen to anything that matches them.
Tell your endpoint when mail arrives, instead of making you poll.
A documented HTTP API with issuable, scopable, revocable keys.
A TypeScript client first, then the rest.
A body written once, versioned, and sent many times: from the composer, from your own code, or by an agent.
One address, or everything from a domain, stopped before it reaches you.
Nearby
Other jobs for the same inbox.
Send, read and organise mail from your own code with a typed client.
Give every ticket, record or customer its own address, with nothing to create.
Mail arriving at your domain reaches your server as a signed webhook, seconds later.
