NevTan Mail is secure, ad-free business email on your own custom domain, with a built-in calendar, meetings, admin controls, and a REST API with webhooks. This guide shows you how to make your inbox trigger actions in other tools automatically — logging every enquiry to a spreadsheet, creating a task when a client emails, posting to Slack when an invoice lands — without writing a line of code. For the wider product picture, see our complete NevTan Mail platform guide.
A webhook sends your mailbox events to a URL the moment they happen. Zapier gives you that URL through its Catch Hook trigger. You paste the URL into NevTan Mail's webhook settings, send yourself a test email, and Zapier picks it up with every field parsed and ready to map into any of its thousands of connected apps. Total setup time is about ten minutes. The only requirement with a cost attached is that Webhooks by Zapier is a premium app, so it needs a paid Zapier plan — the Free plan cannot use it.
Webhooks vs IMAP vs API: Which One You Actually Want
Three ways exist to connect email to another system, and people regularly pick the wrong one.
IMAP is for reading a mailbox like a mail client does. Zapier can connect to an inbox over IMAP, but it works by polling — checking every few minutes to see whether anything new arrived. That means a delay, it burns tasks on every check, and it breaks in awkward ways with folders and read states.
A REST API is for asking questions and giving commands: fetch this message, search for that, send a reply. It is pull-based. Something has to decide to ask.
A webhook is the inverse. Instead of you asking "anything new?", the mail platform tells you the instant something happens, by making an HTTP POST to a URL you nominate. No polling, no delay, no wasted checks.
For automation, webhooks are almost always the right answer, because the thing you want is "when an email arrives, do something" — and that is precisely the shape of a webhook. Our detailed comparison of IMAP, SMTP, and API integrations covers when each of the three is genuinely the better fit.
One practical difference worth noting up front: Zapier's polling triggers check for new data on an interval that depends on your plan — as slow as every 15 minutes on the Free plan. Webhooks fire the moment the event occurs. If you are automating anything customer-facing, that gap matters.
What You Need Before Starting
Four things.
A business email account on your own domain. Webhooks fire on mailbox events, so you need a mailbox you control at the platform level rather than a consumer address. If you are not set up yet, start with our guide to business email on your own domain.
API and webhook access on your plan. In NevTan Mail this lives in the developer settings alongside your API keys. Check your current plan before you start building, since availability of API and webhook features can differ by tier — our features page lists what is included where, and the terms of service cover API usage conditions.
A paid Zapier account. This is the one hard requirement with a price attached. Webhooks by Zapier is classified as a premium app and is not available on Zapier's Free plan. Zapier restructured its plans and raised prices during 2026, and published figures vary considerably between sources, so check zapier.com for current tiers rather than trusting any number you read in a blog post — including this one.
A destination. Decide what should happen when the email arrives: a row in a spreadsheet, a card on a board, a Slack message, a CRM record. A Zap with no clear destination becomes a Zap nobody maintains.
Step-by-Step Guide
Step 1: Create the Zap and Get Your Webhook URL
In Zapier, create a new Zap. For the trigger app, search for and select Webhooks by Zapier. For the trigger event, choose Catch Hook.
Zapier will generate a unique URL that looks like https://hooks.zapier.com/hooks/catch/1234567/abcdefg/. Copy it. This URL is the address NevTan Mail will send your mailbox events to.
Two event types are offered and the distinction matters. Catch Hook parses the incoming JSON body into individual fields you can map in later steps — this is what you want in almost every case. Catch Raw Hook passes through the unparsed body and the request headers, which you only need if the payload is not JSON, or if you intend to verify a signature header (covered in Step 5).
Pro Tip: Treat the webhook URL as a credential, not a setting. Anyone who has it can POST data into your Zap and trigger whatever it does downstream. Do not paste it into a shared document, a support ticket, or a public repository.
Step 2: Register the URL in NevTan Mail
Open your NevTan Mail developer settings, go to webhooks, and add a new endpoint using the URL you copied.
Then choose which events should fire it. NevTan Mail emits three:
email.received— fires when a message arrives in the mailbox. This is the trigger behind most useful automations.email.sent— fires when a message is sent from the mailbox. Useful for logging outbound activity and for tracking what your team has actually committed to in writing.mailbox.created— fires when a new mailbox is provisioned on your domain. This is the one for onboarding automation: new hire gets a mailbox, and their accounts, tasks, and welcome sequence all follow automatically.
Subscribe only to the events you need. Every delivery becomes a Zapier task, and tasks are the unit you pay for.
Pro Tip: If you are automating a shared address like
support@orinvoices@rather than a personal mailbox, point the webhook at that mailbox specifically. Firing on every message to every mailbox on the domain is the fastest way to exhaust a monthly task allowance on mail nobody needed automated.
Step 3: Send a Test Email
Back in Zapier, the trigger step will be waiting to receive test data. Send an ordinary email to the mailbox you configured.
Within a second or two, Zapier should report that it caught a hook. Click into the test record and you will see the payload broken into fields: sender address, sender name, recipient, subject, body text, timestamp, message ID, and attachment information.
This is the moment the whole thing becomes "no code." You now have structured, named fields that you can drag into any later step. Nothing has to be parsed by hand.
Pro Tip: Send a realistic test, not "test test test". Zapier builds its field mapping from the sample payload it receives, and if your test email has no attachment, no reply-to, and a one-word body, some fields will be absent from the sample and harder to map later. Send something that looks like the real thing you are automating.
Step 4: Add Your Action
Now add the second step — what should happen with that email.
Pick the destination app, choose the action, and map the fields from Step 3 into it. If it is Google Sheets, map sender to one column, subject to another, timestamp to a third. If it is Slack, compose a message that embeds the sender and subject. If it is a CRM, map the sender address to the contact lookup field.
Add a Filter step between the trigger and the action if you only want some emails to flow through. Filtering on the subject line containing "invoice", or on the sender domain matching a specific client, is the most common refinement and it protects your task budget. This is also the point where well-structured subject lines pay off for reasons beyond readability — predictable subject lines make reliable filters.
Test the Zap, then turn it on.
Step 5: Secure the Endpoint
Your webhook URL is publicly reachable by design. Anyone who learns it can send it fabricated data. For a Zap that writes to a spreadsheet, the stakes are low; for a Zap that creates records in a CRM or posts to a customer-facing channel, they are not.
Two layers of protection, in order of effort:
A shared secret in the query string. Append a token to the URL you register — https://hooks.zapier.com/hooks/catch/1234567/abcdefg/?secret=your-long-random-string — and add a Filter step in Zapier that only continues when that field matches. Anyone POSTing without the token gets stopped at the filter. This takes two minutes and defeats casual abuse.
Signature verification. NevTan Mail can sign each payload with a secret so you can confirm it genuinely came from us. Verifying that signature requires reading the raw request headers, which means using Catch Raw Hook plus a Code step — so it is not strictly no-code. For most small-business automations the shared secret is proportionate; for anything touching money or customer records, do the signature check.
Pro Tip: Webhook payloads contain the content of your email — sender, subject, and usually the body. That data leaves your mailbox and lands in Zapier and every downstream app in the chain. Before you connect anything, check what each app retains and where. Our overview of email encryption for business explains what protection does and does not travel with the message, and our privacy policy sets out how we handle your data on our side.
Step 6: Watch It for a Week
New Zaps fail quietly. Check Zapier's Task History after a few days and look for errored runs and for runs that fired when they should not have. Tighten your filter if the volume is higher than expected.
Eight Automations Worth Actually Building
Skip the ones that sound clever and build these.
1. Log every enquiry to a spreadsheet. email.received on your sales address → append a row with sender, subject, and timestamp. The simplest possible Zap and the one most small businesses get the most from, because it turns an inbox into a dataset you can count.
2. Create a task when a client emails. email.received, filtered to your client domains → create a task with the subject as the title and a due date two days out. Nothing falls through. If your tasks already live beside your mail, as described in our guide to email, calendar, and tasks in one workspace, you may not need Zapier for this at all — check before you build.
3. Post new support email to a Slack channel. email.received on support@ → Slack message. Gives the whole team visibility without everyone needing mailbox access.
4. Add new enquirers to your CRM. email.received → search CRM for the sender address → create the contact if no match. Use a Filter plus a Search step so you are not creating duplicates on every follow-up.
5. Onboard new staff automatically. mailbox.created → create their project tool account, add them to the team directory, send the welcome pack. The underused event of the three, and the highest-leverage one for growing teams.
6. Archive invoices to cloud storage. email.received filtered on attachments and a subject containing "invoice" → save the attachment to a dated folder. Your accountant will thank you in January.
7. Log outbound commitments. email.sent filtered to key accounts → append to a spreadsheet. A surprisingly useful record of what was promised, to whom, and when.
8. Summarise long emails before you read them. email.received → an AI step that produces a two-line summary → post it to you. Our piece on how AI is changing the inbox covers where this is heading and what it does well.
A caution on automated sending: if you add a Zap step that sends email — an auto-acknowledgement, say — you are now generating automated mail, and it is subject to the same deliverability rules as everything else you send. Make sure your authentication is in order, per our guide to domain authentication, keep automated acknowledgements distinct from marketing sends as covered in transactional vs marketing emails, and follow our email deliverability best practices so your automated replies do not quietly start landing in spam.
Real Example
A six-person design studio was losing enquiries. Everything arrived at hello@ — new business, invoices, supplier mail, newsletters — and two people checked it inconsistently. They could not say how many enquiries they received in a month, let alone how many they converted.
They built two Zaps in an afternoon.
The first fires on email.received at hello@, filters out anything from their known supplier domains and anything with "unsubscribe" in the body, and appends a row to a Google Sheet: date, sender, subject, and a blank status column. The second fires on the same event with a tighter filter — first-time senders only — and posts to a Slack channel called #new-enquiries with a reply button.
Nothing about this required code. The entire configuration was pasting a URL, picking two events, and dragging fields into two actions.
Two outcomes. The obvious one is that response time to new enquiries dropped from days to hours, because the Slack message was visible to everyone rather than sitting in a mailbox two people half-owned.
The second outcome mattered more. After a month they had a spreadsheet with 47 rows, and they could see for the first time that roughly a third of their enquiries arrived on Friday afternoons and had historically sat unanswered until Monday. That was not an automation problem; it was a staffing problem they had been unable to see. The webhook did not fix it, but it made it visible, and that is frequently the real return on this kind of automation.
How Webhook Delivery Actually Works
Four mechanics worth understanding, because they explain most of the problems people hit.
Delivery is an HTTP POST with a JSON body. When email.received fires, NevTan Mail makes a POST request to your registered URL carrying a JSON object describing the event. Zapier's Catch Hook parses that JSON and exposes each key as a mappable field. That parsing is what makes this no-code — without it you would be writing string-handling logic.
Failures are retried, but not forever. If your endpoint is unreachable or returns an error, NevTan Mail retries the delivery, up to 12 attempts. This handles transient outages well. It does not handle a misconfigured endpoint — if your Zap is turned off, or the URL is wrong, the retries exhaust and the event is gone. Always confirm your Zap is switched on before you rely on it.
Zapier always answers 200 OK. Catch Hook returns a standard success response and cannot be configured to return a custom status code or response body. This is fine for one-way notification, which is what mailbox events are. It means Zapier cannot be used to build an endpoint that needs to answer the caller with data — and it means a Zap that fails internally still returned a success to us, so Zapier's own Task History is where you look for failures, not our delivery log.
Rate limits apply on both sides. NevTan Mail's REST API permits 120 requests per minute per key. Zapier counts each action step as a task against your monthly allowance, with its own limits per plan. The practical consequence: a two-step Zap on a mailbox receiving 500 emails a month consumes around 500 tasks if you do not filter. Filters that stop a run before the action step are the main lever for controlling this, which is why Step 4 recommends adding one early rather than later.
A related security note: a webhook endpoint is an unauthenticated URL that causes things to happen. That is a useful mental model for why the Step 5 protections matter — and the same reasoning behind verifying inbound mail, covered in our explainer on phishing protection and TLS encryption.
Common Mistakes to Avoid
Mistake 1: Subscribing to every event on every mailbox. The fastest route to an exhausted task allowance. Solution: Subscribe one mailbox to one event, add a filter, and expand only once it works.
Mistake 2: Building the Zap and never checking it again. Zaps fail silently when a downstream app changes its fields or an authorisation lapses. Solution: Review Task History weekly for the first month.
Mistake 3: Testing with a one-word email. Zapier maps fields from your sample payload; a thin sample produces thin mapping. Solution: Test with a message that resembles the real thing, including an attachment if attachments matter.
Mistake 4: Leaving the endpoint completely open. Your Zap will act on anything POSTed to that URL. Solution: Add the shared-secret filter — two minutes of work.
Mistake 5: Using a webhook where the platform already has the feature. Auto-replies, filters, labels, and forwarding are built into most business email platforms and cost nothing to run. Rebuilding an out-of-office responder in Zapier burns tasks to do worse what your mail platform already does — see our guide to out-of-office automation. Solution: Check the native feature list before you automate.
Mistake 6: Forgetting the payload contains email content. Connecting a mailbox to five apps means your correspondence is now in five places with five retention policies. Solution: Audit the chain before building, especially for mailboxes that receive anything confidential.
Mistake 7: Assuming a turned-off Zap queues events. It does not. Retries exhaust and the event is lost. Solution: Turn the Zap on before registering the webhook, not after.
Frequently Asked Questions
Do I need to know how to code to use webhooks with Zapier?
No. Setting up a Catch Hook requires copying a URL from Zapier and pasting it into your email platform's webhook settings. Zapier parses the incoming JSON into named fields that you drag into later steps. The only part that genuinely requires code is cryptographic signature verification, which needs Catch Raw Hook plus a Code step — and a shared secret in the query string is a no-code alternative that covers most needs.
Is Webhooks by Zapier free?
No. Webhooks by Zapier is a premium app and is not available on Zapier's Free plan, so a paid plan is required. Zapier changed its plan structure and pricing during 2026 and published figures vary widely between sources, so check zapier.com directly for current tiers.
What is the difference between Catch Hook and Catch Raw Hook?
Catch Hook parses the incoming JSON or form body into individual fields ready to map — the right choice for almost every use case. Catch Raw Hook delivers the unparsed body along with the request headers, which you need for non-JSON payloads such as XML, or when verifying a signature header in a Code step.
What email events can trigger a Zap?
NevTan Mail emits email.received when a message arrives, email.sent when a message is sent from the mailbox, and mailbox.created when a new mailbox is provisioned on your domain. Most automations are built on email.received; mailbox.created is the one to use for staff onboarding workflows.
What happens if Zapier is down when an email arrives?
NevTan Mail retries failed webhook deliveries up to 12 times, which covers transient outages. It does not cover a Zap that is switched off or a URL that is wrong — in those cases the retries exhaust and the event is not delivered. Confirm the Zap is on before relying on it.
Should I use webhooks or IMAP to connect my email to Zapier?
Webhooks, in almost every case. IMAP requires Zapier to poll your mailbox on an interval, which introduces delay and consumes tasks on every check regardless of whether anything arrived. Webhooks push the event the instant it happens. IMAP is the better fit only when you need to read historical mail rather than react to new mail.
How many Zapier tasks will this use?
Roughly one task per action step per triggered event. A two-step Zap on a mailbox receiving 500 messages a month will consume around 500 tasks if unfiltered. Adding a Filter step that stops most runs before the action is the main way to control cost.
Is it safe to send my email content to Zapier?
It is a decision to make deliberately rather than a yes or no. The webhook payload includes sender, subject, and typically the message body, and that content then travels to every app in the Zap. Review what each service retains before connecting mailboxes that handle confidential material, and secure the endpoint itself with a shared secret at minimum.
Automate From an Inbox That Was Built For It
Webhooks turn your mailbox from a place where work arrives into a place where work starts. The setup is ten minutes, the ongoing cost is a handful of Zapier tasks, and the result is that nothing sits unnoticed in a shared inbox again.
NevTan Mail gives you the pieces to build on: email.received, email.sent, and mailbox.created webhooks with retry handling, a REST API for reading, searching, sending, and replying at 120 requests per minute per key, admin keys for provisioning mailboxes, plus secure, ad-free business email on your own domain with calendar, meetings, and role-based admin controls. Our features page sets out what is included, and the principles behind the product explain how we think about building it.
If you are weighing the cost of getting set up, our guide to cheap business email for startups compares the realistic options, and our piece on why teams are switching to modern webmail covers what you get beyond the API. For more on deliverability once your automations start sending, see why emails go to spam and how to fix it. Everything else is on the NevTan Mail blog.
Ready to connect your inbox to everything else you use? Start your free trial with NevTan Mail today.
