Here's a frustrating scenario you've probably encountered: Your accounting software sends invoice PDFs via email. Your e-commerce platform emails order confirmations. Your monitoring tools fire off alerts to your inbox. All these systems work perfectly fine—except they're stuck in 2010, communicating exclusively through email.
Meanwhile, your shiny new automation workflows in Make.com, n8n, or Zapier are sitting there waiting for webhook triggers that never come. You're left manually copying data from emails into your systems, or worse, building fragile email polling scripts that break every time someone changes an email template.
That's where Mail Hook comes in. Think of it as a translator between the email world and the webhook world. You get a unique email address (something like [email protected]), point your old systems at it, and boom—every email becomes a webhook trigger with all the data neatly structured and ready to use. No coding, no complex setup, just copy and paste.
Create a Mail Hook in seconds—just enter your webhook URL and get your unique email address
Let me paint you a picture. You've spent weeks building this beautiful automation workflow. Orders come in, inventory updates automatically, shipping labels print, customers get tracking numbers—it's a thing of beauty. Except there's one problem: your supplier's system from 2015 only sends order confirmations via email. No API. No webhooks. Just good old-fashioned email.
Sound familiar? You're not alone. I've seen this pattern everywhere:
The usual workaround? Either someone manually copies data from emails (soul-crushing), or you build an email polling script that checks your inbox every few minutes (fragile and breaks constantly). Neither option is great, and both waste time that could be spent on actual work.
Here's the concept: Mail Hook gives you a unique email address that acts as a bridge. When any email lands in that inbox, it immediately fires off a webhook to wherever you want—Make.com, n8n, Zapier, or your own custom endpoint. The email gets parsed automatically, and all the important bits (subject, sender, body, attachments) get packaged up in a nice JSON format ready for your automation to consume.
The setup is almost embarrassingly simple. I'm talking 30 seconds, tops:
The whole process:
[email protected]
Every email is parsed and delivered with complete details—subject, sender, body, attachments, and metadata
Every email that hits your Mail Hook gets automatically parsed and sent to your webhook with everything you need. You get the subject line, who sent it, the full email body (both plain text and HTML versions), any attachments with direct download links, plus all the technical metadata like timestamps and message IDs if you need them for more advanced workflows.
The nice thing is it's all structured and consistent. No matter what format the original email was in, your webhook always receives the same clean data structure. Makes building workflows much easier when you're not constantly dealing with edge cases.
You don't really need to know the technical details (it just works), but if you're curious: when an email hits your Mail Hook address, it gets received by our mail servers, parsed to extract all the relevant data, and then immediately fires off a webhook to your endpoint. The whole thing happens in about 1-2 seconds.
Any attachments get uploaded to secure storage and you receive direct download URLs that work for 60 days. No need to worry about email size limits or attachment handling—it's all taken care of automatically.
Someone (or some system) sends an email to your Mail Hook address. They don't need to do anything special—it's just a regular email.
We extract the subject, sender, body, attachments—basically everything useful from the email.
Your webhook endpoint gets called with all the parsed data. Usually happens within a second or two.
Make.com, n8n, or Zapier picks up the webhook and runs whatever workflow you've built. Magic happens.
Enough theory. Let's talk about actual scenarios where this saves people hours every week.
This is probably the most common use case I see. Your accounting software emails invoices as PDFs, but you want them automatically logged in your system. Maybe you're using Airtable to track everything, or you need them in QuickBooks, or you just want a Slack notification so your accounting team knows there's a new invoice to review.
Here's how it works:
Takes about 5 minutes to set up, saves hours of manual data entry every month.
Got a contact form that only emails you? (I'm looking at you, every WordPress site ever built before 2020.) Point it at a Mail Hook and suddenly those emails become proper support tickets in Zendesk, Freshdesk, or whatever ticketing system you use.
The flow:
No more manually creating tickets from emails. No more missed support requests because someone forgot to check the shared inbox.
Here's a fun one: you're working with a supplier whose e-commerce system is... let's call it "vintage." They email you order confirmations, but your warehouse management system needs webhook triggers to update inventory. Mail Hook to the rescue.
What happens:
Turns a manual process that used to take 10-15 minutes per order into something that happens automatically in seconds.
Your monitoring tool sends email alerts when something breaks. That's great, except emails aren't exactly the best way to wake someone up at 3 AM. With Mail Hook, those alerts can trigger PagerDuty incidents, send SMS messages to your on-call engineer, and post to your Slack incidents channel—all automatically.
How it works:
Way better than relying on someone checking their email at 3 AM.
You know those old contact forms that just email you the submission? The ones where you have to manually copy the person's info into your CRM? Yeah, those. Point them at a Mail Hook and suddenly every form submission becomes a proper lead in HubSpot, Salesforce, or whatever CRM you're using.
The automation:
No more leads falling through the cracks because someone forgot to check the contact form email.
If you're using n8n, you're in luck—there's a native CustomJS node that makes this ridiculously easy. No webhook URLs to copy, no manual configuration. Just install the node and you're good to go.
That's it. The trigger node gives you all the email data—subject, sender, body in both plain text and HTML, attachments with download URLs, all the metadata. Just connect it to the rest of your workflow and you're done.
Make.com users have two options, both super straightforward. Pick whichever one fits your workflow better.
Easiest if you're already using other CustomJS features:
More flexible if you want full control:
Here's a simple scenario you can build in Make.com's visual builder in about 5 minutes:
No code required. Just drag, drop, and connect the modules.
Zapier doesn't have a native Mail Hook integration (yet), but the standard webhook trigger works perfectly fine. Takes maybe a minute to set up.
đź’ˇ Mail Hook vs. Zapier's Email Parser
Yeah, Zapier has its own email parser. But Mail Hook is better for a few reasons: you get instant setup (no template configuration), complete data including HTML body and attachments with download URLs, and the same Mail Hook works across Zapier, Make, n8n, and your own custom APIs. More flexible.
Once the webhook fires, you've got all the email data to work with. Here's how to actually use it in your workflows.
Need to extract an invoice number or order ID from the email body? Every automation platform has built-in tools for this. Make.com has its Text Parser module, n8n has Extract from Text nodes, Zapier has Formatter. They all work basically the same way—you tell them what pattern to look for (like "Invoice #" followed by numbers) and they pull it out for you. No coding required.
You get both versions of every email. Plain text is easier to parse for simple stuff. HTML is useful when you need to extract data from specific elements (like pulling numbers out of a table), or when you want to preserve the formatting for display somewhere.
Attachments come through as download URLs. So if someone emails an invoice PDF to your Mail Hook, you get a direct link to download that PDF. From there, you can grab it with an HTTP Request node and upload it to Google Drive, Dropbox, S3, wherever you need it. The URLs work for 60 days, which is plenty of time for any reasonable workflow.
Your Mail Hook email address should be treated as a secret:
Secure your webhook endpoints:
CustomJS Mail Hook is included in all CustomJS plans:
Limits:
Pretty much instant. Emails usually trigger webhooks within 1-2 seconds. Sometimes a bit longer if there's high load, but we're talking 5-10 seconds max, not minutes.
Yep, as many as you want. Each one gets its own unique email address and can point to a different webhook. Useful if you want separate Mail Hooks for invoices, support tickets, alerts, etc.
We retry failed webhooks automatically—3 times with increasing delays (1 minute, 5 minutes, 15 minutes). If all 3 fail, you can manually retry from the dashboard. The email data is stored for 60 days so you won't lose anything.
Yes. You can set up filters based on sender email, subject line keywords, or whether there are attachments. Prevents spam or unwanted emails from triggering your workflows.
Each email in a thread triggers its own webhook. The email headers include thread info (In-Reply-To, References) so you can group related emails in your workflow if you need to.
Nope, they're receive-only. Security thing—prevents people from using Mail Hooks to send spam.
Just send an email to your Mail Hook address from Gmail or whatever email client you use. The webhook fires immediately and you can see the data in your automation platform. Super easy to test.
Look, the reality is that a lot of business-critical systems still communicate via email. Your accounting software, your suppliers' order systems, your monitoring tools—they're not going away anytime soon, and most of them aren't getting webhook support added.
Mail Hook is basically a translator. It sits between your email-based systems and your modern automation workflows, converting those emails into webhook triggers that Make.com, n8n, or Zapier can actually work with. No more manual data entry, no more fragile email polling scripts, no more leads falling through the cracks.
Setup takes about 30 seconds. Create a Mail Hook, copy the email address, paste your webhook URL. Done. Then every email becomes a structured webhook with all the data you need—subject, sender, body, attachments, everything.
If you're tired of manually processing emails or building hacky workarounds, give it a shot. First 600 emails per month are free.
Continue reading on similar topics
Automate lead generation and user onboarding with form webhooks. Connect forms to Make.com, n8n, and Zapier for instant CRM updates, email sequences, and team notifications. 600 free submissions/month.
Detaillierter Vergleich: CustomJS Form Builder vs. Typeform, Jotform & Google Forms. Welcher Builder passt zu deinem Workflow? Make.com & n8n Integration, Custom Domains, Webhooks.
Generate HTML forms with AI (no form builder) and send submissions to webhooks that trigger Make.com and n8n workflows. Includes copy-paste code and best practices.