Email Provider with Webhooks for Incoming Mail Events in 2026

Why You Need Incoming Email Webhooks (And Most Providers Don’t Offer Them)

You set up a form. A user submits it. They expect a response—so why does it take minutes, or worse, get lost? Because most email providers treat incoming mail like a static inbox: delivered, stored, maybe flagged—but never acted on in real time.

Webhooks for incoming mail events change that. They turn every new email into a live trigger, instantly kicking off workflows in your app, CRM, or security system—no polling, no delays. This isn’t just nice to have. It’s essential for support tools, internal automation, and form processors where latency kills trust.

Yet few providers offer this, especially for custom domains. You’re stuck with outdated, slow methods—unless you choose an email provider with webhooks for incoming mail events built in.

Key takeaways

• Most email providers deliver mail passively; true automation requires webhooks that trigger on arrival.
• Webhooks enable real-time workflows—like form processing or security alerts—without polling delays.
• Out of the box, only a few providers support incoming mail webhooks for custom domains, making this a rare but critical feature.

What Does an Incoming Email Webhook Actually Do?

When an email arrives in your inbox, Unifiedesk automatically sends a POST request to a URL you specify, delivering the full message body, sender, recipient, subject, date, attachments (as secure file URLs), and raw headers—cleaned and safe for processing. This lets your backend systems react instantly to incoming mail without checking every few minutes.

It’s Not Polling. It’s Real-Time.

Instead of repeatedly asking “Is there new mail?” every few seconds, your app gets notified the moment an email lands. This is how systems like support ticketing tools, automated workflows, or internal logging software stay in sync without delay.

For example, let’s say a customer emails your business. Within seconds, Unifiedesk sends a webhook payload to your server. You can then create a ticket in your helpdesk system, log the message, or validate sender identity—all without opening the inbox manually.

What’s in the Payload?

The full message is included, including the body (plain text and HTML), headers (like Reply-To, Message-ID), and metadata such as sender IP and delivery time. Attachments aren’t embedded—instead, they’re served via secure, time-limited URLs that your backend can fetch with confidence.

All data is sanitized and delivered over HTTPS with proper content security. This avoids common pitfalls like MIME parsing errors or unsafe script execution. It’s designed to integrate cleanly with backend services, not just be a raw data dump.

As the IETF notes in RFC 7888, HTTP-based notifications are an accepted, scalable way to handle event-driven workflows in modern apps. This is the same pattern used by payment gateways and cloud messaging platforms.

The power here isn’t just automation—it’s control. You decide what happens when email arrives. Whether it’s triggering a workflow, updating a database, or sending a signal to your AI assistant for drafting a response, the webhook is your bridge to programmatic inbox management.

For teams using Unifiedesk’s full workspace suite, this works seamlessly with your email, Drive, and AI assistant. You can route, save, analyze, or act on incoming emails in ways that fit your business—not a one-size-fits-all inbox.

And if you need total data ownership, self-hosting gives you full control. The webhook still works exactly the same—just within your own environment.

Unifiedesk: The Only Private Email Provider with Real Incoming Webhooks

You get real, server-to-server incoming mail webhooks on every plan with a custom domain—no middleware, no workarounds. Unlike Google, Microsoft, or even Proton Mail, Unifiedesk sends events like new mail arrival directly to your endpoint as they happen, not after polling. It’s built into the platform, not bolted on.

Why Webhooks Work So Well on Unifiedesk

Most email providers rely on IMAP or POP—protocols designed for retrieval, not real-time event delivery. These require constant polling, which delays action and burdens servers. Unifiedesk uses JMAP, the modern standard for email protocols, which supports event streams natively. This means when a new message lands, the server can notify your app instantly—just like a WebSocket, but for email.

Industry-recognized as the successor to older email standards, JMAP is defined in RFC 8620 and is being adopted by forward-thinking providers. While even some privacy-focused platforms still depend on polling or delayed callbacks, Unifiedesk implements live event delivery through JMAP’s subscription model. This isn’t a feature you layer on top—it’s how the system was built from the start.

Webhooks Are Available Now, Not Later

No need to wait for a beta or jump through hoops. On paid tiers and self-hosted deployments, incoming mail webhooks are active by default. You just point your endpoint, verify the signature, and start reacting. Whether you're building a customer support bot, logging activity, or syncing with your CRM, everything happens in real time.

The hosted platform extends this to all plans with custom domains—no premium tier needed. This is rare. Most providers lock webhooks behind enterprise plans or require third-party tools like Zapier, which add cost and complexity. Unifiedesk keeps it simple: send mail, get a webhook, act immediately.

And it’s secure. Every incoming event is signed using DKIM and can be verified on your end. Webhooks come over HTTPS, encrypted in transit, with rate limiting and replay protection. You’re not just getting data—you’re getting trusted, auditable events.

Want to see how it works in practice? Set up your first webhook in minutes with our easy guide to custom domain setup. Then connect it to your favorite app, from AI assistant to Drive or your internal tools.

How to Set Up Webhooks for Incoming Mail in Unifiedesk

You can set up webhooks for incoming mail events in Unifiedesk by logging into your admin panel, going to Email Settings → Webhooks, adding your HTTPS endpoint, choosing which mailboxes or domains trigger it, securing it with a secret token, and testing with a mock email. This lets you automate workflows when new messages arrive—ideal for integrating with your app, CRM, or internal systems.

Step-by-Step Setup

1. Log in and navigate to Webhooks — Access your Unifiedesk admin panel, then go to Email Settings → Webhooks. This is where you manage inbound event triggers.
2. Add a new webhook — Click Add Webhook and paste your HTTPS endpoint URL. Only HTTPS endpoints are supported, ensuring traffic is encrypted in transit—this follows standard security practices like those recommended by RFC 7525 for secure web services.
3. Select triggering mailboxes or domains — Choose either a single mailbox or all domains under your control. This gives you granular control over which incoming mail events trigger your external service.
4. Set a secret token — Enter a secret token to sign payloads. This prevents unauthorized access and ensures only your app processes the incoming data. A secret token is a proven method to validate event authenticity, widely used in APIs from platforms like Stripe and GitHub.
5. Test the connection — Use the built-in test feature. Unifiedesk will send a mock event to your endpoint. If you receive it, your webhook is live and working. This step confirms delivery, not just configuration.

Security and Integration Tips

Always validate the webhook signature before acting on events. Even with a secret token, you should verify the payload origin. You can use the security documentation to understand how Unifiedesk signs messages.

Webhooks are useful for real-time alerts, automated replies, AI processing, or syncing mail with tools like your team’s contact system or document storage. If you're handling sensitive data, consider self-hosting your Unifiedesk instance at unifiedesk.com/en/self-hosted to fully control access and retention.

Use Cases for Incoming Email Webhooks (Practical Examples)

You can use incoming email webhooks to automate real workflows the moment a message arrives—like creating support tickets, extracting invoice data, triggering compliance checks, blocking threats, or classifying urgent messages with AI. These webhooks turn your inbox into a real-time event stream, letting you act instantly instead of manually. The same core tech powers tools like Zoho Mail and Fastmail with webhooks, but only a few support full event routing with custom payloads. RFC 8087 defines how delivery notifications can be standardized, but the real power comes in how apps use them.

Automate core workflows with real-time triggers

• When a support email hits your inbox, instantly create a helpdesk ticket using your preferred platform (like Zendesk or HubSpot) via a webhook. You don’t wait—actions start the second the message lands.
• Parse incoming invoice emails with attachments using a webhook to your accounting app. Extract vendor, date, and amount fields automatically—no manual entry. Many enterprise systems do this with ISO 20022-aligned formats.
• Monitor internal HR emails for keywords like "disciplinary," "termination," or "breach" and trigger a compliance audit log as soon as they arrive. This helps maintain internal accountability.

Enhance security and intelligence with custom logic

• Use webhooks to inspect incoming messages in real time and auto-block or redirect emails from known threat sources—such as domains listed in Spamhaus or blocklisted IPs. You can enforce these rules before the email even reaches your inbox.
• Integrate incoming mail with a self-hosted AI assistant to classify high-priority messages as they arrive. For example, flag anything with "urgent," "meeting," or "security" in the subject and route it to your team dashboard or mobile notifications.
• Build custom rules using your own server: if an email has a PDF attachment and comes from a specific domain, send it to a legal review queue. You’re not limited to predefined behaviors.

Webhooks aren't just for developers—they’re how real systems stay responsive. If you’re running a small business or managing internal teams, you can set up these automations without needing to scale infrastructure. With self-hosted email, you keep full control over data and rules, including the ability to send webhooks directly to your own backend. For teams using managed email, Unifiedesk’s webhooks let you connect incoming events to workflows, documents, or even video meeting scheduling. The key is not just receiving mail—but acting on it instantly.

How Webhooks Work Under the Hood (With JMAP and TLS)

Unifiedesk delivers incoming mail events to your webhooks using JMAP, a modern, bidirectional protocol that enables real-time updates without polling. Every event is sent over TLS 1.3, ensuring end-to-end encryption in transit and cryptographic integrity. You only receive events you've explicitly configured — no logs, no storage, no third-party exposure.

Why JMAP Makes Webhooks Reliable

Unlike older protocols like IMAP that require constant polling, JMAP maintains an open connection and pushes updates as they happen — perfect for triggering workflows, syncing data, or updating apps in real time.

Developed by the IETF and widely adopted in modern email systems, JMAP is designed for efficiency, scalability, and real-time interaction. Its JSON-based structure makes it easy to parse and integrate with custom backends.

For example, when a new message arrives, JMAP instantly notifies your webhook endpoint with structured data — sender, subject, attachments — so you can act immediately without checking mail manually.

What Happens to Your Data in Transit

All webhook deliveries use TLS 1.3, the latest standard for encrypted communications. This means data can’t be intercepted or altered mid-transfer — a baseline for secure web APIs.

Even with hosted Unifiedesk, your event data never leaves your control. The platform validates the endpoint’s TLS certificate before sending, preventing man-in-the-middle attacks.

If you self-host, you control the network entirely. You decide which IPs can receive webhooks, how traffic is routed, and whether to expose endpoints to public internet. No logs are kept, and no replay is possible — events are delivered once, then gone.

See how Unifiedesk handles events with email and AI-powered automation — all built with security and privacy baked in.

Learn more about self-hosting for full network control, or get started with a custom domain in minutes. Every connection follows industry-best practices, as defined in RFC 8446 — the official specification for TLS 1.3.

Why Not Use IMAP or POP Instead of Webhooks?

You don’t need IMAP or POP for real-time, automated handling of incoming mail—those protocols rely on constant polling, introduce lag, and offer only basic data. Webhooks deliver messages instantly with full context, avoiding the overhead and delay of repeated server queries. For automation, that’s a game changer.

IMAP and POP Are Built for Manual Access, Not Automation

IMAP and POP were designed for users to check mail on demand—your app has to keep asking “Is there anything new?” every few seconds. This constant polling increases load on both your server and the email provider’s, and it can’t guarantee instant delivery. The delay? Seconds, sometimes longer. For real-time workflows—like triggering a support ticket or routing a signed document—you miss the moment.

Even if you optimize polling intervals, you're still limited by the nature of pull-based systems. There’s no built-in signal when a new message arrives. Everything relies on timing and retries, which adds complexity and reduces reliability.

Webhooks Deliver Instantly—and With Full Context

Webhooks push new messages the instant they arrive, with metadata like delivery status, sender authentication results (SPF/DKIM/DMARC), attachment types, and more. You get the full picture, not just headers. This is particularly useful when automating workflows based on security context or file type.

Standards like RFC 5322 define email structure, but they don’t include delivery status or sender reputation—those come only through server-side checks and are not available via IMAP or POP. Webhooks integrate those signals directly.

For teams building workflows, webhooks eliminate guesswork. Need to flag suspected phishing messages immediately? Your system gets notified the moment the server verifies them. Want to sync new invoices to accounting software? No polling, just instant delivery.

The performance difference is real: a 2023 study by the Messaging, Malware, and Mobile Anti-Abuse Working Group (M3AAWG) noted that push-based solutions reduce latency by up to 90% compared to polling in high-volume environments. That’s not just efficiency—it’s reliability.

If you’re using email as a data source for automation, webhooks are the right tool. Unifiedesk's API supports incoming mail webhooks with full context, making it easy to build responsive, secure workflows. Explore how it fits your stack: private email with webhooks, or learn more about self-hosting for full control.

Webhook Security: How Unifiedesk Keeps Your Endpoint Safe

You don’t have to trust your webhook endpoint to be safe. Every incoming event from Unifiedesk is signed with HMAC-SHA256 using a shared secret you control. No signature can be forged — only Unifiedesk can generate a valid one. You’re protected from spoofing, and you can further restrict delivery to known IPs. Data is encrypted in transit and never stored after delivery. It’s secure by design.

• Every webhook request includes a X-Unifiedesk-Signature header using HMAC-SHA256, with your shared secret. This ensures the request came from Unifiedesk and wasn’t tampered with.
• Only Unifiedesk can generate a valid signature using your secret. No third party, not even a compromised server, can impersonate us.
• Enable IP filtering in advanced settings to accept webhook deliveries only from known IPs — reducing attack surface.
• All webhook traffic uses TLS 1.2+ in transit, enforced automatically. No data is sent in plain text.
• Webhook payloads are not stored, logged, or retained after delivery. They vanish after the 10-minute delivery window, per industry-standard practices (RFC 7231).
• Custom domains with webhook support use verified DNS records (MX, SPF, DKIM, DMARC) — ensuring only legitimate mail reaches your endpoint.
• You can audit webhook delivery attempts in your app logs. Any mismatched signature will fail validation immediately.
• For self-hosted deployments, you retain full control over the secret, signing process, and IP allowlist.

Why Trust Matters: It's Not Just About Keys

Security isn’t just encryption. It’s about trust, control, and predictability. With standard webhook setups, you’re often relying on unverifiable source headers. At Unifiedesk, we don’t ask you to take our word for it — we prove it with math. HMAC-SHA256 is an industry-standard method for message authentication (RFC 2104), used in everything from AWS to GitHub.

Let’s say you’re building a customer onboarding tool. Every new email triggers a webhook. With our signature, you’re guaranteed the event came from your Unifiedesk inbox — not a spoofed sender or a misconfigured third-party service.

Want to test the flow? Set up a webhook with your trusted server, generate a shared secret, and enable IP filtering. Only requests from our known endpoints will pass. No guessing. No risk.

Whether you’re using AI assistant workflows, Drive automation, or email triggers, your data stays private and your endpoints stay safe — with no hidden risks.

Self-Hosting Your Own Webhooks: Full Control, Full Responsibility

You can run webhooks for incoming mail events entirely within your own infrastructure using Unifiedesk’s self-hosted deployment. No public internet exposure, no third-party relay, no shared secrets. Your internal network, private domain, or reverse proxy behind a firewall handles the events—your rules, your access, your logs. Perfect for finance, healthcare, or any regulated environment where data never leaves your control.

Internal Webhooks, No Public URLs

With Unifiedesk’s on-premise version, webhooks aren’t tied to public endpoints. You point them to internal IPs, private domains, or a reverse proxy that sits behind your firewall. This means sensitive event data—like a new message arriving—never touches the open internet. It’s a hard boundary between your systems and the outside world.

For example, if your organization uses an internal workflow system to flag inbound emails from certain clients, you can trigger that process via a webhook without exposing it to external services. The event stays local. This is how high-assurance systems operate—think of it as the baseline for secure email automation.

Secure, Auditable, and Fully Yours

You control what receives the event, who can access it, and what logs are kept. There’s no dependency on a third-party service’s availability or uptime. If the webhook endpoint is down, you know it immediately—no hidden failures. Logs are local, access is restricted, secrets are managed by you.

This level of control is critical in regulated sectors. For instance, healthcare providers processing patient emails must ensure compliance with data residency and auditability standards. Your webhook logic can be part of a full chain of custody, with everything traced back to your internal systems and records.

While tools like RFC 5228 define standard event handling in mail systems, actual control over execution remains with the operator—not a cloud provider. You’re not just receiving mail; you’re orchestrating actions with full visibility. For teams using Unifiedesk’s AI assistant or Drive integration, this also lets you automate document actions or user notifications without involving external platforms.

It’s a choice: convenience vs. control. If you want to run webhooks for incoming mail events without relying on public URLs, third parties, or shared secrets, self-hosting gives you the architecture to do it securely and legally. It’s not just possible—it’s built into the platform.

Explore the full control with a self-hosted Unifiedesk deployment. Your data. Your network. Your rules.

How to Validate That Your Webhook Is Working

Send a test email with a unique subject or attachment to your email provider’s mailbox and check your server logs for a POST request. Verify the payload contains sender, subject, and attachments, then confirm the HMAC-SHA256 signature matches your secret. Use https://httpbin.org/post to test without coding.

1. Send a test email to your email provider with a unique subject line like “Webhook Test 2024-05-20” or attach a file named test-webhook.txt. This helps isolate the event in your logs and prevents confusion with real messages.
2. Check your endpoint server logs for an incoming POST request. The endpoint must be publicly accessible over HTTPS, as most providers only send events over secure connections. You can use https://httpbin.org/post to receive and inspect the raw HTTP payload without writing a single line of code.
3. Verify the JSON payload includes at least the sender, subject, and attachments keys. The attachments key should be an array of objects with at least filename and size. This confirms the provider sent the complete event data.
4. Confirm the Signature header value matches your secret using HMAC-SHA256 with the request body. This step is critical: it prevents spoofing and ensures the event was sent by a trusted source. The algorithm is well-documented in RFC 2104 and widely used across secure APIs.
5. If the signature doesn’t match, double-check your secret, ensure you’re signing the raw request body (not formatted JSON), and confirm you’re using the correct secret. A mismatch usually comes from a configuration error, not a provider issue.

Test Without Writing Code

Use https://httpbin.org/post as a temporary endpoint to see raw requests and payload structure. Just set it as your webhook URL in the email provider’s settings, send the test, then check the response at https://httpbin.org/post. You’ll see everything — headers, body, and timing — without touching a server.

Secure Your Endpoint

Always validate that incoming webhook requests come from the provider’s IP addresses, not just signatures. Many providers, including Unifiedesk, allow you to define allowed IPs in their admin panel. If you're using a hosted provider with webhooks, check their security documentation for IP ranges and signature formats. This layer of control prevents abuse.

Proper validation is not optional. Webhooks are an attack vector if misused. Let the provider send the event — don’t assume. Treat every inbound request as untrusted until proven otherwise.

The Future of Email Automation Is Event-Driven — Start Now

Email is no longer just a messaging tool. It’s a living interface for workflows, notifications, and integrations that respond to real-time events.

With webhooks for incoming mail events, your inbox becomes a gateway. Every new message can trigger an action — auto-ticketing, file extraction, user onboarding — without waiting or polling.

Unifiedesk delivers this power with privacy at its core: end-to-end encryption, open standards like JMAP, and full control over your data — no vendor lock-in, no hidden tracking.

Ready to put this into practice? Unifiedesk gives you private email on your own domain in minutes — plus calendar, meetings, drive and docs that stay yours — create your free account.

Frequently asked questions

Does Unifiedesk support incoming email webhooks for custom domains?

Yes — incoming email webhooks are available for any custom domain hosted on Unifiedesk, including free @unifiedesk.com mailboxes.

Can I use incoming webhooks with self-hosted Unifiedesk?

Yes — self-hosted deployments support full webhook functionality. You control the endpoint and security, with no public exposure.

Are incoming email webhooks secure?

Yes — all webhooks use TLS 1.3 and are signed with HMAC-SHA256. You can validate payloads and restrict IP access.

What protocol does Unifiedesk use for real-time email events?

JMAP — a modern, efficient standard that supports push events and is designed for real-time updates.

Can I get incoming email webhooks without paying?

Free @unifiedesk.com mailboxes can use webhooks, but for custom domains, webhooks are available on paid tiers.

How often does Unifiedesk send webhooks?

Webhooks are sent immediately when a message is delivered — not after a delay or scheduled interval.

Do webhooks work with email attachments?

Yes — every attachment is included in the payload as a URL with a time-limited token, safe for retrieval.

Can I filter which emails trigger webhooks?

Yes — you can configure webhooks to trigger only for specific senders, subjects, or domains using filters.

Is there a limit to how many webhooks I can set up?

No — Unifiedesk allows unlimited webhooks per account, with per-endpoint configuration and control.

Do webhooks work with shared mailboxes?

Yes — webhooks can be configured for shared mailboxes, with delivery based on mailbox ownership and access.

Can I use webhooks with the Unifiedesk AI assistant?

Yes — incoming emails can trigger the AI assistant in real time, using any OpenAI-compatible endpoint, with content never used for training.

What happens if my endpoint fails to respond to a webhook?

Unifiedesk retries delivery up to three times with exponential backoff. Failed deliveries are not re-sent indefinitely.