Custom payload configuration

With Business+ plans, you can configure exactly which fields are included in your webhook payload on a per-alias basis. Strip what you don't need, keep what you do.

Why customise your payload

Minimise PII exposure

Every field you forward is a field that could end up in logs, error reports, or third-party systems. If your pipeline only needs the sender address and subject line to route a support ticket, there is no reason to forward the full email body.

Stripping unnecessary fields reduces your data footprint and simplifies GDPR compliance — you can't leak data you never received.

Reduce overhead

Smaller payloads mean faster webhook delivery, lower bandwidth, and less processing on your end. At high volumes the difference adds up: a metadata-only payload can be an order of magnitude smaller than one carrying the full HTML body and inline attachments.

Match rigid endpoints

Some webhook receivers — Zapier, Make, or internal microservices — expect a specific schema. If the endpoint has no flexibility for extra fields, a trimmed payload avoids parsing errors and simplifies your integration.

Compliance and audit

Regulated industries often require data minimisation by design. Custom payloads let you enforce this at the source: forward only the metadata you need, and leave everything else behind.

How it works

In your alias settings, select which field groups to include:

Field group	What it contains	Default
Sender & recipients	From, To, CC, BCC addresses	Included
Subject	Email subject line	Included
Text body	Plain-text version of the email	Included
HTML body	Raw HTML version of the email	Included
Markdown body	Cleaned Markdown conversion	Included
Links	Extracted URLs from the email body	Included
Attachments	File metadata and content/URLs	Included
Envelope data	SMTP routing info (MAIL FROM, RCPT TO)	Excluded
Spam analysis	Spam score, DKIM/SPF/DMARC results	Plan-dependent

Disable any group you don't need. The payload will only contain the fields you've selected.

Example: metadata-only payload

A support ticketing system that only needs routing information:

{
  "message": {
    "sender": {
      "name": "Alice Martin",
      "email": "alice@acme.com"
    },
    "recipient": "support@yourcompany.com",
    "subject": "Order #1042 — delivery question"
  }
}

No email body, no attachments, no HTML. Just enough to create a ticket and notify the right team.

Example: attachments only

A document processing pipeline that extracts invoices from emails:

{
  "message": {
    "sender": {
      "email": "billing@vendor.com"
    },
    "subject": "Invoice #4821",
    "attachments": [
      {
        "filename": "invoice-4821.pdf",
        "contentType": "application/pdf",
        "size": 48210,
        "downloadUrl": "https://app.emailconnect.eu/attachments/.../download"
      }
    ]
  }
}

The email body is irrelevant — only the PDF matters.

Availability

Custom payload configuration is available on Business and Platform plans. On lower plans, all available fields are included automatically.