[{"data":1,"prerenderedAt":13},["ShallowReactive",2],{"$f3bV2J-TX1y2X4SCZmKsgjVf9t39hLRTBSlv9yf2vzBk":3},{"title":4,"slug":5,"excerpt":6,"category":7,"order":8,"screens":9,"html":12},"Custom payload configuration","custom-payload","Choose exactly which fields your webhook receives — reduce overhead, limit PII exposure, and match endpoint requirements","configuration",7,[10,11],"webhooks","aliases","\u003Cp>With \u003Cstrong>Business+\u003C\u002Fstrong> 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.\u003C\u002Fp>\n\u003Ch2>Why customise your payload\u003C\u002Fh2>\n\u003Ch3>Minimise PII exposure\u003C\u002Fh3>\n\u003Cp>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.\u003C\u002Fp>\n\u003Cp>Stripping unnecessary fields reduces your data footprint and simplifies GDPR compliance — you can't leak data you never received.\u003C\u002Fp>\n\u003Ch3>Reduce overhead\u003C\u002Fh3>\n\u003Cp>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.\u003C\u002Fp>\n\u003Ch3>Match rigid endpoints\u003C\u002Fh3>\n\u003Cp>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.\u003C\u002Fp>\n\u003Ch3>Compliance and audit\u003C\u002Fh3>\n\u003Cp>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.\u003C\u002Fp>\n\u003Ch2>How it works\u003C\u002Fh2>\n\u003Cp>In your alias settings, select which field groups to include:\u003C\u002Fp>\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Field group\u003C\u002Fth>\n\u003Cth>What it contains\u003C\u002Fth>\n\u003Cth>Default\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>\u003Cstrong>Sender & recipients\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>From, To, CC, BCC addresses\u003C\u002Ftd>\n\u003Ctd>Included\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Subject\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>Email subject line\u003C\u002Ftd>\n\u003Ctd>Included\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Text body\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>Plain-text version of the email\u003C\u002Ftd>\n\u003Ctd>Included\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>HTML body\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>Raw HTML version of the email\u003C\u002Ftd>\n\u003Ctd>Included\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Markdown body\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>Cleaned Markdown conversion\u003C\u002Ftd>\n\u003Ctd>Included\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Links\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>Extracted URLs from the email body\u003C\u002Ftd>\n\u003Ctd>Included\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Attachments\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>File metadata and content\u002FURLs\u003C\u002Ftd>\n\u003Ctd>Included\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Envelope data\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>SMTP routing info (MAIL FROM, RCPT TO)\u003C\u002Ftd>\n\u003Ctd>Excluded\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Spam analysis\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>Spam score, DKIM\u002FSPF\u002FDMARC results\u003C\u002Ftd>\n\u003Ctd>Plan-dependent\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\n\u003Cp>Disable any group you don't need. The payload will only contain the fields you've selected.\u003C\u002Fp>\n\u003Ch2>Example: metadata-only payload\u003C\u002Fh2>\n\u003Cp>A support ticketing system that only needs routing information:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-json\">{\n  "message": {\n    "sender": {\n      "name": "Alice Martin",\n      "email": "alice@acme.com"\n    },\n    "recipient": "support@yourcompany.com",\n    "subject": "Order #1042 — delivery question"\n  }\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>No email body, no attachments, no HTML. Just enough to create a ticket and notify the right team.\u003C\u002Fp>\n\u003Ch2>Example: attachments only\u003C\u002Fh2>\n\u003Cp>A document processing pipeline that extracts invoices from emails:\u003C\u002Fp>\n\u003Cpre>\u003Ccode class=\"language-json\">{\n  "message": {\n    "sender": {\n      "email": "billing@vendor.com"\n    },\n    "subject": "Invoice #4821",\n    "attachments": [\n      {\n        "filename": "invoice-4821.pdf",\n        "contentType": "application\u002Fpdf",\n        "size": 48210,\n        "downloadUrl": "https:\u002F\u002Fapp.emailconnect.eu\u002Fattachments\u002F...\u002Fdownload"\n      }\n    ]\n  }\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>The email body is irrelevant — only the PDF matters.\u003C\u002Fp>\n\u003Ch2>Availability\u003C\u002Fh2>\n\u003Cp>Custom payload configuration is available on \u003Cstrong>Business\u003C\u002Fstrong> and \u003Cstrong>Platform\u003C\u002Fstrong> plans. On lower plans, all available fields are included automatically.\u003C\u002Fp>\n\u003Ch2>Related topics\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Ca href=\"\u002Fhelp\u002Falias-options-explained\u002F\">Alias options explained\u003C\u002Fa> — all alias configuration options\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"\u002Fhelp\u002Fwebhook-payload-reference\u002F\">Webhook payload reference\u003C\u002Fa> — full payload field documentation\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"\u002Fhelp\u002Fdata-retention\u002F\">Data retention\u003C\u002Fa> — how long data is stored\u003C\u002Fli>\n\u003C\u002Ful>\n",1781207679711]