Email-in setup overview
How inbound mail reaches Nura24 — the three moving parts, and which one needs which configuration.
The user-facing version is at Email-in. This article is for the person actually setting up the pipeline.
The three moving parts
- Your mail provider (Gmail, Microsoft 365, Fastmail, your own MX) — where customer emails arrive.
- A parsing webhook provider (Postmark Inbound, Mailgun Routes, Amazon SES + SNS) — receives the raw email and POSTs parsed JSON to us.
- Nura24 — accepts the POST at
/api/email/inbound, creates the ticket.
Two delivery patterns
A. Direct to the parsing provider
You give customers an address that already points at the parsing provider's MX (e.g. an address on a domain whose MX records you've pointed at Postmark Inbound). The parser gets the email, posts to us. No forwarding step.
This is fastest and most reliable. Postmark and Mailgun both let you allocate an inbound subdomain (inbox.acme.com) whose MX you set to their servers. The address becomes tickets@inbox.acme.com or whatever you choose.
B. Forwarding from your existing inbox
You keep your customer-facing address (support@acme.com) on your existing mail provider, and add a forwarding rule that sends every message to your parsing provider's catch-all address.
Slightly slower (one extra hop), and forwarded mail sometimes loses headers, but doesn't require touching MX records.
What Nura24 needs
Just one thing: the parsing provider must POST parsed email to:
POST https://api.nura24.com/email/inbound
with an Authorization: Bearer <secret> header (or X-Inbound-Secret, or ?secret= query) where <secret> is the shared key configured on our side as EMAIL_INBOUND_SECRET.
The payload format is provider-agnostic. We look for sender/recipient/subject/body across multiple key variants — Postmark's, Mailgun's, SES's — and use whichever's present.
The recipient address
For Nura24 to route an inbound message to a workspace, the parser must POST a recipient address of the form:
tickets+<inbox-token>@<EMAIL_INBOUND_DOMAIN>
where <inbox-token> is the per-workspace token from Tickets → Inbox and <EMAIL_INBOUND_DOMAIN> is whatever domain we've registered as the inbound destination at the platform level.
Provider-specific setup
We don't have a Cloud-only / Amazon SES walkthrough yet because most people use Postmark or Mailgun for this. If you need SES, contact us.