A webhook, but for email
Every workflow can have its own email address. Send or forward a message to it and the workflow runs in seconds, with the parsed message as input. No mailbox to connect, no polling, nothing to host.
- doneMailhook received0ms · sender allowlisted
- doneExtract invoice fields1.2s · AI agent
- runningRecord in accountingrunning · NetSuite
- queuedNotify financequeued · Slack
From inbox to running workflow
Generate the address
One click in the workflow designer. Pick an optional prefix like invoices or support-intake; Spojit adds an unguessable random token.
Point mail at it
Paste the address into a vendor portal, a notification setting, or a forwarding rule in your mail client. Anything that can send email can trigger the workflow.
The workflow runs
Delivery is push, not polling. Within seconds the run starts with the parsed message: sender, subject, body, and attachment list.
Built for production, not demos
Push delivery
Runs start seconds after the message arrives. No polling interval, no waiting for the next check.
No mailbox required
Nothing to host and nothing to connect. No inbox to manage, no credentials to look after, nothing that can expire and silently stop your runs.
Sender and subject filters
Allowlist senders by address or domain, and match subjects with a regex. Anything else is dropped before it reaches the workflow.
One-click rotation
Address leaked further than you wanted? Regenerate it. The old address stops working immediately, and mail to it is discarded without a bounce.
Custom prefixes
Name the address for what it does: invoices-, support-intake-, crm-sync-. Easy to spot in forwarding rules and audit logs.
Safe by construction
The address is a cryptographically random capability. Duplicate deliveries are deduplicated, and unknown addresses reveal nothing.
Wherever the work arrives as email
invoices-x7k2m9qf4a3vbn8c@mailhook.spojit.comVendor invoices
Paste the address into your vendor portal as the billing contact. Each invoice email lands in your accounting workflow, not a shared inbox.
support-intake-b2w8rk5e9d7m1pza@mailhook.spojit.comSupport intake
Forward a slice of your support inbox to a mailhook. Triage, classify, and create tickets with an AI agent step.
reports-e3c6n0tj8h2q4vxs@mailhook.spojit.comLegacy systems
That on-prem system that can only send email reports? Its reports now feed a modern workflow with zero changes on its side.
alerts-m9d4g7ka1f5w2hbn@mailhook.spojit.comEmail-only SaaS notifications
Plenty of tools only notify by email. A mailhook turns those notifications into structured workflow inputs.
Mailhook or webhook
Same idea, different transport. Both give a workflow an address the outside world can hit.
Pick a mailhook when
- The sender is a person, a mail client rule, or a system that can only send email
- You want zero setup on the sending side beyond typing an address
- The payload is a message: invoices, reports, notifications, requests
Pick a webhook when
- The sender is software that can make an HTTP request
- You want signed, verified payloads and a response with an execution id
- The payload is structured JSON from an app like Shopify, GitHub, or Slack
Your workflow's new address
Generate a mailhook on the free plan and trigger your first run with a single email. No card needed.