| URI: | /github-webhook/ |
|---|---|
| STATUS: | 400 |
| MESSAGE: | Signature was expected, but not provided |
| SERVLET: | Stapler |
Hi, I can't log in since this morning…
", "to": ["5519fb0d-…@in.webhookrelay-mail.com"], "spf": "pass", "dkim": "pass", "dmarc": "pass", "attachments": [ { "name": "screenshot.png", "content_type": "image/png", "size": 48213, "content": "iVBORw0KGgo…" } ] } ``` You get the sender, subject, both body parts, all headers, the SPF/DKIM/DMARC results, and attachments (base64-encoded). The full [payload reference](https://webhookrelay.com/docs/email/payload/) lists every field, and you can [restrict senders and cap attachments](https://webhookrelay.com/docs/email/filtering-and-policy/) per input. ## [Forwarding](#forwarding) Because the parsed email becomes an ordinary event on the bucket, you can do anything you'd do with a webhook: forward it to your endpoint (public or [behind a firewall](https://webhookrelay.com/webhooks/)), fan it out to several destinations, retry on failure, and [transform it in flight](https://webhookrelay.com/docs/webhooks/functions/) into whatever shape the destination expects. Build that message visually with the [Slack/Discord/Teams formatter](https://webhookrelay.com/webhook-message-formatter/). ## [Examples](#examples) Step-by-step tutorials for the common destinations: - [Email → Slack](https://webhookrelay.com/docs/tutorials/email/slack/) — post inbound email into a Slack channel - [Email → Discord](https://webhookrelay.com/docs/tutorials/email/discord/) — route email to a Discord channel - [Email → Microsoft Teams](https://webhookrelay.com/docs/tutorials/email/microsoft-teams/) — post a Teams card per email - [Email → Google Sheets](https://webhookrelay.com/docs/tutorials/email/google-sheets/) — append a row per email - [Email → Airtable](https://webhookrelay.com/docs/tutorials/email/airtable/) — create an Airtable record - [Email → Notion](https://webhookrelay.com/docs/tutorials/email/notion/) — create a page in a Notion database - [Email → your API](https://webhookrelay.com/docs/tutorials/email/api/) — POST email to your own endpoint - [Email → a database](https://webhookrelay.com/docs/tutorials/email/database/) — insert every email into your DB ## [Get started](#get-started) [Create an email input](https://my.webhookrelay.com) on a bucket, or read [the email docs](https://webhookrelay.com/docs/email/). It works on the free tier — same as any other Webhook Relay input. ## **Frequently asked questions** ### **How do I receive an email as a webhook?** Add an email input to a bucket in Webhook Relay. You get a unique address likehtml body
", "spf": "pass", "dkim": "pass", "dmarc": "pass", "attachments": [ { "name": "resume.pdf", "content_type": "application/pdf", "size": 48213, "content": "html body
", "spf": "pass", "dkim": "pass", "dmarc": "pass", "attachments": [] } ``` See the full [payload reference](https://webhookrelay.com/docs/email/payload/) for every field, including `to`, `cc`, `message_id` and the raw `headers` map. ## [Setup](#setup) **1. Create a bucket.** This is the container that ties an input to its outputs. **2. Add an email input.** Webhook Relay gives you back a unique address of the form `html body
", "spf": "pass", "dkim": "pass", "dmarc": "pass", "attachments": [ { "name": "invoice.pdf", "content_type": "application/pdf", "size": 48213, "content": "html body
", "headers": {}, "spf": "pass", "dkim": "pass", "dmarc": "pass", "attachments": [ { "name": "invoice.pdf", "content_type": "application/pdf", "size": 48213, "content": "html body
", "spf": "pass", "dkim": "pass", "dmarc": "pass", "attachments": [ { "name": "invoice.pdf", "content_type": "application/pdf", "size": 48213, "content": "db-01 root volume is at 92%.
", "headers": {}, "spf": "pass", "dkim": "pass", "dmarc": "pass", "attachments": [ { "name": "report.csv", "content_type": "text/csv", "size": 1024, "content": "", "truncated": false } ] } ``` ## [Step 3: Add the Teams output](#step-3-add-the-teams-output) Add an output to the bucket and set its destination to your **Teams Incoming Webhook** URL (created via a Power Automate Workflow, or a legacy Office 365 connector). Keep that URL handy — it's where the transformed message gets delivered. ## [Step 4: Attach a transform](#step-4-attach-a-transform) Right now the parsed email would be POSTed to Teams as-is, and Teams would reject it because the shape is wrong. Attach a [transform function](https://webhookrelay.com/docs/webhooks/functions/) to the output to convert the parsed email into a Teams **MessageCard**: ``` const email = JSON.parse(r.body); const card = { "@type": "MessageCard", "@context": "https://schema.org/extensions", summary: email.subject, title: email.subject, text: \`**From:** ${email.from_name || email.from}\n\n${email.text}\` }; r.setBody(JSON.stringify(card)); r.setHeader("Content-Type", "application/json"); ``` The function reads `r.body` (the parsed-email JSON string), pulls out the subject, sender and body, and writes a MessageCard back with `r.setBody()`. Setting `Content-Type: application/json` with `r.setHeader()` ensures Teams accepts it. You can also call `r.setResponseStatus()` if you need to control the response returned to the sender. **A note on Adaptive Cards.** Microsoft is migrating Incoming Webhooks away from Office 365 connectors toward Power Automate Workflows, where the modern format is an **Adaptive Card** wrapped in an `attachments` array. The pattern is identical — parse the email, build the card object, `r.setBody(JSON.stringify(...))` — only the JSON shape differs to match whichever URL you were given. ## [Step 5: Test it](#step-5-test-it) Send a plain email to your `HTML body...
", "headers": {}, "spf": "pass", "dkim": "pass", "dmarc": "pass", "attachments": [] } ``` See the full [payload reference](https://webhookrelay.com/docs/email/payload/) for every field. ## [Step 1: Create a bucket and add an email input](#step-1-create-a-bucket-and-add-an-email-input) In the dashboard, create a bucket, then add an **email input** to it. Webhook Relay generates a unique address: ``` 8c2f1e3a-...-d9b4@in.webhookrelay-mail.com ``` Anything sent to that address is parsed and forwarded to the bucket's outputs. Set up forwarding to that address from your provider, or use it directly as the destination on your forms and order system. ## [Step 2: Deploy a Google Apps Script Web App](#step-2-deploy-a-google-apps-script-web-app) Create a Google Sheet, open **Extensions → Apps Script**, and replace the default code with a `doPost(e)` handler that appends a row: ``` function doPost(e) { const sheet = SpreadsheetApp.openById("YOUR_SHEET_ID").getSheets()[0]; const email = JSON.parse(e.postData.contents); sheet.appendRow([ email.date || new Date(), email.from, email.subject, email.text, ]); return ContentService .createTextOutput(JSON.stringify({ status: "ok" })) .setMimeType(ContentService.MimeType.JSON); } ``` Click **Deploy → New deployment**, choose **Web app**, set **Execute as: Me** and **Who has access: Anyone**, then deploy and copy the **Web app URL**. It looks like `https://script.google.com/macros/s/AKfyc.../exec`. Re-publish a new version whenever you change the script. ## [Step 3: Add the Web App URL as a bucket output](#step-3-add-the-web-app-url-as-a-bucket-output) Back in Webhook Relay, add an **output** to your bucket and paste the Apps Script **Web app URL** as the destination. Now every parsed email is POSTed there and appended as a row. ## [Step 4 (optional): Transform to pick columns](#step-4-optional-transform-to-pick-columns) The parsed email JSON carries far more than you probably want in a spreadsheet. Attach a [transform function](https://webhookrelay.com/docs/webhooks/functions/) to the output to reduce it to exactly the columns you'll write: ``` const e = JSON.parse(r.body); r.setBody(JSON.stringify({ date: e.date, from: e.from, subject: e.subject, body: e.text })); ``` This keeps the four fields the Apps Script reads and drops the rest — headers, HTML, auth results — so the row stays clean. Adjust the keys here and the `appendRow([...])` call together to capture whatever you need. ## [Step 5: Send a test email](#step-5-send-a-test-email) Send a message to your `@in.webhookrelay-mail.com` address. Within a second or two a new row — date, from, subject, body — appears in your sheet. If nothing shows up, open the bucket's request log to see exactly what was received, parsed, and delivered. ## [Going further](#going-further) **Fan out to other automation.** If you'd rather not use Apps Script, point the output at any other endpoint that appends rows — a serverless function, an n8n/Make webhook, or your own API. The parsed JSON is the same; only the destination changes. **Forward only some senders.** You don't have to log everything. Use [input filtering and policy](https://webhookrelay.com/docs/email/filtering-and-policy/) to accept mail only from trusted senders or domains and drop the rest before parsing. **Capture more columns.** Add fields in both the transform body and the `appendRow([...])` call — recipient, message IDs, SPF/DKIM/DMARC results — to build a richer log straight from your inbox. This is one of Webhook Relay's [Email to Webhook](https://webhookrelay.com/email-to-webhook/) recipes: give any inbox a programmable address, parse each message to JSON, and route it anywhere. Google Sheets is just one destination — the same pattern delivers parsed email to a database, a chat channel, or an internal API. ## [Get started](#get-started) [Create a free Webhook Relay account](https://my.webhookrelay.com/register), add an email input to a bucket, and turn your inbox into a spreadsheet in a few minutes. Did this page help you? --- --- title: Outbound throttling: control webhook delivery speed meta: "og: title": "Outbound throttling: control webhook delivery speed" description: Pace outgoing webhooks to a steady rate or fixed concurrency. Outbound throttling protects fragile endpoints and respects downstream rate limits. url: https://webhookrelay.com/docs/webhooks/outbound-throttling.md file: /docs/webhooks/outbound-throttling.md --- Hi, your invoice is attached.
", "headers": { "From": "Jon Snowhtml body
", "spf": "pass", "dkim": "pass", "dmarc": "pass" } ``` See the full [payload reference](https://webhookrelay.com/docs/email/payload/) for every field. ## [Get started](#get-started) [Create a free Webhook Relay account](https://my.webhookrelay.com/register), add the Email Trigger, and turn support requests, alerts and form submissions into n8n workflows — no IMAP or mailbox required. Receiving **HTTP webhooks** too? See the [n8n Webhook Trigger](https://webhookrelay.com/docs/tutorials/n8n/webhook-trigger/). Did this page help you? --- --- title: TLS Compatibility: Custom & Legacy TLS Versions meta: "og: title": "TLS Compatibility: Custom & Legacy TLS Versions" description: Receive webhooks from legacy systems that can't speak modern TLS. Set a minimum TLS version per input, accept TLS 1.0/1.1, and skip verification per output. url: https://webhookrelay.com/features/tls-compatibility.md file: /features/tls-compatibility.md ---  **Plans: Business** FEATURES # **TLS Compatibility: Custom & Legacy TLS Versions** Receive webhooks from legacy systems that can't speak modern TLS. Set a minimum TLS version per input, accept TLS 1.0/1.1, and skip verification per output. **Some systems are stuck in the past — your security baseline shouldn't be.** A legacy device, an old ERP, or an on-prem appliance that can only speak TLS 1.0/1.1 (or an outdated cipher) simply _can't deliver_ a webhook to a modern endpoint that has, correctly, disabled those protocols. Webhook Relay's **TLS compatibility** lets that one old sender through — on a single input — while everything else stays on modern TLS. ## [The problem: a legacy sender meets a modern endpoint](#the-problem-a-legacy-sender-meets-a-modern-endpoint) When an old system tries to POST a webhook over a TLS version or cipher the receiver has disabled, neither side will budge, and the delivery dies with one of these: ``` curl: (35) error:0A000102:SSL routines::unsupported protocol error:14094410:SSL routines:ssl3_read_bytes:sslv3 alert handshake failure javax.net.ssl.SSLHandshakeException: Received fatal alert: protocol_version ERR_SSL_VERSION_OR_CIPHER_MISMATCH ``` The usual "fix" is to lower TLS everywhere the old sender might reach — weakening your whole stack for one stubborn box. (For a full reference of these errors and what each means, see the [TLS/SSL error guide](https://webhookrelay.com/docs/webhooks/tls-ssl-errors/).) ## [The solution: relax TLS on one input, not everywhere](#the-solution-relax-tls-on-one-input-not-everywhere) Give the legacy sender a Webhook Relay **input** and set the TLS policy on that input alone. Each input has a **TLS compatibility** setting with two controls: - **Custom minimum TLS version** — the lowest version the input will accept. The default is TLS 1.3; lower it to TLS 1.2 for senders that still require it (PayPal webhooks, for example). _(Business and Pro)_ - **Legacy TLS compatibility (TLS 1.0 + wide ciphers)** — one toggle that makes the input accept TLS versions down to 1.0 and a wider legacy cipher set, for the oldest systems that can't do anything newer. _(Pro)_  Webhook Relay completes the old handshake on that input, then forwards the event onward over modern TLS. The legacy sender finally gets through, and the rest of your traffic never leaves TLS 1.2/1.3. ## [Deliver to self-signed and internal certificates](#deliver-to-self-signed-and-internal-certificates) The other half of the gap is on the delivery side. When you forward to an internal service or legacy box whose certificate isn't signed by a public CA, strict clients fail with `certificate verify failed` or `unable to verify the first certificate`. Webhook Relay exposes a per-destination **TLS verification** toggle under **Delivery controls** — switch it off for that one endpoint and the webhook is delivered.  Only disable verification for destinations you control and trust, typically on a private network. ## [Why a relay is the right place to solve it](#why-a-relay-is-the-right-place-to-solve-it) - **One input, not a fleet of clients.** Relax TLS on the single input a legacy sender uses, instead of lowering the security baseline everywhere it might connect. - **Contain the risk.** Legacy settings apply **per input domain**, so the rest of your inputs keep enforcing modern TLS 1.3. - **Enforce a minimum, too.** Pin a custom minimum TLS version on an input to satisfy a compliance requirement and reject anything weaker. - **Reach internal endpoints.** Deliver onward to services behind your firewall through the [Webhook Relay agent](https://webhookrelay.com/features/webhook-to-internal-server/) — self-signed certificate and all. ## [Where it earns its keep](#where-it-earns-its-keep) - **Legacy on-prem and IoT senders.** Appliances, controllers and old ERPs that will never get a TLS upgrade but still need to emit events. - **Integrations pinned to TLS 1.2.** Senders like PayPal that require a specific older version to connect. - **Compliance-driven minimums.** Enforce a floor on accepted TLS versions without auditing every producer. - **Internal and self-signed destinations.** Forward to a service whose certificate a public CA would never vouch for. ## [Better together](#better-together) TLS compatibility pairs naturally with [durable retries](https://webhookrelay.com/features/durable-retries/) — persist and retry until the event lands — and [throttling](https://webhookrelay.com/features/throttling/), so a fragile legacy system is never overwhelmed. Ready to let your legacy systems through? [Create a free account](https://my.webhookrelay.com/register), or read the [TLS/SSL error reference](https://webhookrelay.com/docs/webhooks/tls-ssl-errors/) to match the exact error you're seeing.  ## **Start forwarding webhooks in minutes ** Connect a source, pick a destination, and Webhook Relay handles delivery, retries and transforms. Set up your first webhook in under five minutes. [Start for free ->](https://my.webhookrelay.com/register) Free plan · No credit card required · 7-day money-back guarantee on paid plans --- --- title: n8n Webhook Trigger (No Public IP) | WebhookRelay meta: "og: title": "n8n Webhook Trigger (No Public IP)" description: Receive webhooks in self-hosted n8n with no public IP, port forwarding or tunnel. n8n connects out over a WebSocket and is never exposed to the internet. url: https://webhookrelay.com/docs/tutorials/n8n/webhook-trigger.md file: /docs/tutorials/n8n/webhook-trigger.md --- 