MailWebhookMailWebhook
Gmail to Webhook

Turn Gmail messages into JSON webhooks

MailWebhook connects Gmail or Google Workspace mailboxes, optionally scopes monitoring by Gmail label, normalizes each message, and delivers signed JSON webhook events to your application.

Start freeView webhook docs

Built for Gmail webhook, Gmail-to-webhook, Gmail new-email webhook, and Google Workspace inbox automation workflows.

Connected Gmail mailboxwatch active
  • Inbox248
  • Invoices12
  • Support31
  • Starred4

Watching label Invoices

Invoice 1042

billing@vendor.example

POST /webhooks/gmail-email
{
  "schema": { "name": "mailwebhook.generic", "version": "1" },
  "message": {
    "subject": "Invoice 1042",
    "from": [{ "email": "billing@vendor.example" }],
    "to": [{ "email": "ap@company.com" }]
  },
  "meta": {
    "source": "gmail",
    "label": "Invoices",
    "received_at": "2026-06-27T10:14:32Z"
  }
}

Can Gmail trigger a webhook?

Yes, with MailWebhook. Gmail itself does not give every mailbox a simple "POST this email to my webhook URL" setting. MailWebhook connects to Gmail or Google Workspace through Google OAuth, receives Gmail watch notifications, syncs message history, normalizes the email, and posts structured JSON to your webhook endpoint.

You can connect an existing Gmail or Google Workspace mailbox and optionally scope monitoring to a Gmail label so only the messages in that workflow become webhook events.

See the payload example

From Gmail mailbox to signed webhook

A managed pipeline that takes Gmail and Google Workspace email from Google OAuth connection to a signed webhook event your application can trust.

  1. Step 01

    Connect with Google

    Start the Google OAuth flow from MailWebhook and authorize a Gmail or Google Workspace mailbox.

  2. Step 02

    Choose the mailbox scope

    Use the connected mailbox and optionally enter a Gmail label ID to limit which messages are watched.

  3. Step 03

    Receive Gmail notifications

    MailWebhook establishes a Gmail watch against its Pub/Sub topic so mailbox changes can trigger sync.

  4. Step 04

    Sync message history

    The Gmail sync worker uses the stored history cursor to find added messages and fetch raw MIME bytes.

  5. Step 05

    Normalize and map

    Message headers, people, bodies, attachments, timestamps, and extracted fields become stable JSON.

  6. Step 06

    Deliver the webhook

    Send the payload to your endpoint with X-MailWebhook-Signature and X-Idempotency-Key headers.

Create your first Gmail route

A Gmail event your app can process

MailWebhook sends your endpoint the pipeline output directly. For the generic JSON mapper, Gmail messages use the same documented payload contract as other providers, with meta.source set to gmail.

{
  "schema": {
    "name": "mailwebhook.generic",
    "version": "1"
  },
  "event": {
    "id": "6ff49aa1-7050-4ad1-95d9-2711f2ca7e88",
    "project_id": "dca29061-c4a7-4687-a8dd-24d2f26548c7",
    "route_id": "2f3713bf-88cc-46c6-aaa3-ea9d6e9d20f3",
    "created_at": "2026-06-27T10:14:32Z"
  },
  "message": {
    "message_id": "<invoice-1042@vendor.example>",
    "message_id_type": "original",
    "subject": "Invoice 1042",
    "date": "2026-06-27T10:13:59Z",
    "from": [{ "email": "billing@vendor.example", "name": "Vendor Billing" }],
    "to": [{ "email": "ap@company.com", "name": "Accounts Payable" }],
    "headers": {
      "message-id": "<invoice-1042@vendor.example>",
      "content-type": "multipart/mixed"
    }
  },
  "body": {
    "text": "Please review invoice 1042.",
    "attachments": [
      {
        "id": "9f5a1ded-538d-4f5f-a7a9-d3eacf9e58a0",
        "filename": "invoice-1042.pdf",
        "content_type": "application/pdf",
        "size": 93259,
        "is_inline": false,
        "sha256": "059a0f5260487bbe663994de1fd641401fec76ac9f6bddfe5b53ae60d4bb2d86"
      }
    ]
  },
  "meta": {
    "source": "gmail",
    "raw_size_bytes": 26546,
    "received_at": "2026-06-27T10:14:32Z"
  }
}
View webhook payload docs

Built for Gmail and Google Workspace mailbox workflows

Purpose-built for Gmail evaluators, including Google Workspace email webhook and label-scoped Gmail automation.

Intake

Gmail inbox intake

Turn messages from an existing Gmail or Google Workspace mailbox into webhook events.

Scope

Label-scoped automation

Monitor a specific Gmail label ID when only one operational workflow should trigger webhooks.

Normalize

Structured email events

Normalize senders, recipients, headers, bodies, attachments, and timestamps before delivery.

Map

Custom JSON mapping

Shape Gmail messages into the JSON your receiving system expects.

Deliver

Signed webhook delivery

Send events with deterministic idempotency and HMAC signature headers.

Inspect

Message preview and backfill

Preview route output for mailbox messages and backfill Gmail email that arrived before connection.

Compare mailbox options

Use Gmail as an input to your application

Gmail inbound email webhooks power support, finance, sales, operations, and integration workflows across technical and operations teams.

See email data entry automationSee email API for AI agents

  • Support intake

    Turn inbound Gmail messages into support tickets, triage tasks, or AI agent events.

  • Invoices and receipts

    Extract vendor, subject, attachment metadata, and invoice identifiers before webhook delivery.

  • Sales and lead intake

    Route Gmail leads into your CRM or enrichment pipeline with a stable JSON contract.

  • Operations alerts

    Send recurring email notifications from Gmail into internal systems.

  • AI inbox workflows

    Let agents receive mailbox events without granting direct mailbox control to the agent runtime.

  • Legacy system integration

    Connect systems that still send email to modern HTTP workflows.

Gmail API is powerful. The production webhook pipeline is still work.

Gmail gives you useful primitives: OAuth, watch notifications, Pub/Sub messages, history IDs, and raw message fetches. A production Gmail-to-webhook workflow still needs OAuth state, watch renewal, Pub/Sub JWT verification, history cursor handling, history reset recovery, MIME parsing, duplicate handling, attachment policy, payload shaping, webhook signing, retries, and delivery history.

Direct Gmail API build

  • Manage Google OAuth token state and refresh behavior
  • Create and renew Gmail watches against Pub/Sub topics
  • Verify Pub/Sub push requests and map them to mailboxes
  • Maintain history cursors and recover from reset conditions
  • Fetch and parse RFC822 MIME
  • Build idempotency, HMAC signatures, retries, and logs

MailWebhook

  • Connect a Gmail or Google Workspace mailbox through the product flow
  • Use MailWebhook's Gmail watch and sync path
  • Receive mailbox messages through route events
  • Let the Gmail adapter sync added messages from stored account state
  • Receive normalized JSON payloads
  • Use signed webhook delivery and delivery attempt tracking
Start free

Where MailWebhook fits in a Gmail stack

MailWebhook is the operational layer on top of Gmail mailbox access: email intake, normalization, JSON mapping, and signed webhook delivery for the workflows your application depends on.

Compared with Gmail API alone

Gmail API exposes mailbox primitives. MailWebhook packages the email intake, normalization, mapping, and webhook delivery workflow.

Compared with Google Apps Script

Apps Script can work for small automations. MailWebhook is for teams that want route-level JSON payloads, signatures, idempotency, and delivery tracking outside a script project.

Compared with forwarding rules

Forwarding moves email somewhere else. MailWebhook turns mailbox messages into route events and webhook payloads.

Compared with Zapier or Make

No-code workflows are useful for simple routing. MailWebhook focuses on developer-ready JSON payloads and HTTP endpoint delivery.

Compared with parser inbox tools

Parser tools often depend on parser-specific inboxes. MailWebhook supports existing Gmail and Google Workspace mailbox workflows.

Email to webhookEmail webhook APIEmail to JSONMicrosoft 365 to webhookIMAP to webhook

Designed for webhook receivers that need predictable events

  • Signed webhook delivery so your endpoint can verify the sender.
  • An X-Idempotency-Key header so duplicate delivery can be handled safely.
  • Structured payloads so downstream code does not depend on raw email quirks.
  • Route-level configuration so different Gmail workflows can produce different payloads.
  • Message preview so teams can inspect route output before wiring automation into production.
  • Gmail backfill for messages that arrived before the mailbox was connected.
Read webhook security docs

Start free, scale when you need to

The Free plan includes 300 emails/month at no cost. Paid plans start at $29/per month with a 30-day free trial.

See full pricing
  • HMAC-signed webhook delivery
  • Automatic retries with backoff
  • Event inspector and replay
  • Idempotency keys for safe dedupe

Gmail webhook FAQ

Can Gmail trigger a webhook?
Yes, with MailWebhook. Gmail itself does not provide a simple arbitrary webhook URL setting for every new email. MailWebhook connects to Gmail, syncs messages, normalizes email content, and delivers JSON to your webhook endpoint.
Can Google Workspace email trigger a webhook?
Yes. MailWebhook supports Gmail and Google Workspace mailboxes through the Google OAuth connection flow.
Does Gmail have native webhooks?
Gmail supports watch notifications through Gmail API and Google Pub/Sub. MailWebhook uses that kind of provider workflow as part of a full email-to-webhook pipeline that fetches the message, normalizes it, maps JSON, signs delivery, and posts to your endpoint.
Can I trigger a webhook only for labeled Gmail messages?
Yes. MailWebhook supports optional Gmail label scoping. The current product field expects a Gmail label ID to limit which messages are watched.
Do I need to change MX records?
No. For Gmail workflows, MailWebhook connects to an existing Gmail or Google Workspace mailbox through Google OAuth.
Can I use this instead of Gmail forwarding?
Yes, when your goal is to send structured webhook events to an application. Forwarding moves email to another inbox; MailWebhook sends normalized JSON to your endpoint.
Can I backfill Gmail messages?
Yes. MailWebhook's public mailbox docs list Gmail as a supported provider for message backfill, subject to plan day caps and one backfill job at a time.
Can I preview a Gmail message before delivering it to my webhook?
Yes. MailWebhook mailbox preview can run a specific message through a selected route and show the JSON delivered to the endpoint. Preview does not include attachments.
Can I send a custom JSON shape to my webhook?
Yes. You can use the generic normalized payload or map Gmail email fields into a custom JSON payload for the receiving system.
What happens if the same email event is delivered twice?
Webhook receivers should be idempotent. MailWebhook sends an X-Idempotency-Key header so your application can detect and safely ignore duplicate processing.

Turn Gmail mailbox messages into webhook events

Connect a Gmail or Google Workspace mailbox, choose the route, and deliver structured email events to your application without building another Gmail API worker.

Start freeRead the docs