Inbound email webhooks and event routing

Turn inbound email into webhook events for real operating workflows

Use MailSlurp to route inbound email to webhook endpoints in real time. Replace mailbox polling with programmable inboxes, email-to-webhook delivery controls, and workflow routing for support, finance, operations, and reply handling.

Configure webhooks View inbound API

Trusted by top companies worldwide

Product features

MailSlurp capabilities for inbound email webhooks

Turn inbound email into webhook events with programmable inboxes, routing controls, and reliable handoff into support, finance, and operations systems.

Inbox-scoped email-to-webhook events

Attach webhooks to dedicated inboxes so new emails, replies, headers, and attachments are posted into the exact workflow that owns that address.

Learn more

Headers, auth, static IPs, and payload templating

Configure authentication, outbound network behavior, and request-body shaping so customer endpoints can accept MailSlurp events without a translation service in the middle.

Learn more

Payload schemas, signatures, and test sends

Inspect webhook schemas, verify signatures, and run live test deliveries before an event consumer, parser, CRM sync, or ticketing route becomes part of a production workflow.

Learn more

Delivery history, retries, and replay

Track successful and failed deliveries, review unseen errors, and replay failed posts after downstream outages without losing the original event.

Learn more

Support and case routing

Send inbound support email straight into queue consumers or case-management flows with enough metadata to classify, assign, and review exceptions quickly.

Explore

Invoice, receipt, and document intake

Trigger finance or back-office workflows from inbound attachments, vendor email, and parser output without relying on shared inbox triage or mailbox polling jobs.

Explore

Reply capture and order operations

Capture replies, supplier messages, and order email as webhook events so downstream systems can update records, notify owners, or trigger follow-up automation.

Explore

Parse inbound data faster

Convert messages and attachments into structured fields for downstream systems and ops queues.

Explore

Inbox-scoped email-to-webhook events

Attach webhooks to dedicated inboxes so new emails, replies, headers, and attachments are posted into the exact workflow that owns that address.

Learn more

Headers, auth, static IPs, and payload templating

Configure authentication, outbound network behavior, and request-body shaping so customer endpoints can accept MailSlurp events without a translation service in the middle.

Learn more

Payload schemas, signatures, and test sends

Inspect webhook schemas, verify signatures, and run live test deliveries before an event consumer, parser, CRM sync, or ticketing route becomes part of a production workflow.

Learn more

TSserver.ts

// example express server that you control
const app = express();
app.use(bodyParser.json());
// receive new email webhook payload via post
app.post('/new-email-endpoint', async (request, response) => {
  // can use typescript types
  const payload = request.body as WebhookNewEmailPayload;

  // do something with with email id
  expect(payload.emailId).toBeTruthy();

  // return a 2xx status code so MailSlurp knows you received it
  return response.sendStatus(200);
});
const server = app.listen(port);

Receive MailSlurp events in your own webhook handler

Attach a webhook to the inbox, process inbound email events in your application, and keep event handling tied to the exact mailbox that owns the workflow.

Open docs

TSserver.ts

// example express server that you control
const app = express();
app.use(bodyParser.json());
// receive new email webhook payload via post
app.post('/new-email-endpoint', async (request, response) => {
  // can use typescript types
  const payload = request.body as WebhookNewEmailPayload;

  // do something with with email id
  expect(payload.emailId).toBeTruthy();

  // return a 2xx status code so MailSlurp knows you received it
  return response.sendStatus(200);
});
const server = app.listen(port);