| 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/blog/receive-emails-as-webhooks/docs/email/payload/) lists every field, and you can [restrict senders and cap attachments](https://webhookrelay.com/blog/receive-emails-as-webhooks/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/blog/receive-emails-as-webhooks/webhooks/)), fan it out to several destinations, retry on failure, and [transform it in flight](https://webhookrelay.com/blog/receive-emails-as-webhooks/docs/webhooks/functions/) into whatever shape the destination expects. Build that message visually with the [Slack/Discord/Teams formatter](https://webhookrelay.com/blog/receive-emails-as-webhooks/webhook-message-formatter/). ## [Examples](#examples) Step-by-step tutorials for the common destinations: - [Email → Slack](https://webhookrelay.com/blog/receive-emails-as-webhooks/docs/tutorials/email/slack/) — post inbound email into a Slack channel - [Email → Discord](https://webhookrelay.com/blog/receive-emails-as-webhooks/docs/tutorials/email/discord/) — route email to a Discord channel - [Email → Microsoft Teams](https://webhookrelay.com/blog/receive-emails-as-webhooks/docs/tutorials/email/microsoft-teams/) — post a Teams card per email - [Email → Google Sheets](https://webhookrelay.com/blog/receive-emails-as-webhooks/docs/tutorials/email/google-sheets/) — append a row per email - [Email → Airtable](https://webhookrelay.com/blog/receive-emails-as-webhooks/docs/tutorials/email/airtable/) — create an Airtable record - [Email → Notion](https://webhookrelay.com/blog/receive-emails-as-webhooks/docs/tutorials/email/notion/) — create a page in a Notion database - [Email → your API](https://webhookrelay.com/blog/receive-emails-as-webhooks/docs/tutorials/email/api/) — POST email to your own endpoint - [Email → a database](https://webhookrelay.com/blog/receive-emails-as-webhooks/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/blog/receive-emails-as-webhooks/docs/email/). It works on the free tier — same as any other Webhook Relay input. --- --- title: Webhook Relay Blog | WebhookRelay meta: "og: title": "Webhook Relay Blog" description: Guides, tutorials and comparisons for receiving, testing, securing and routing webhooks. url: https://webhookrelay.com/blog.md file: /blog.md --- # **The Webhook Relay Blog ** Guides, tutorials and comparisons for receiving, testing, securing, transforming and routing webhooks — from localhost to production. [**Guides**html body
", "spf": "pass", "dkim": "pass", "dmarc": "pass", "attachments": [] } ``` See the full [payload reference](https://webhookrelay.com/docs/tutorials/email/notion/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
", "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": "resume.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": "HTML body...
", "headers": {}, "spf": "pass", "dkim": "pass", "dmarc": "pass", "attachments": [] } ``` See the full [payload reference](https://webhookrelay.com/docs/tutorials/email/google-sheets/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/tutorials/email/google-sheets/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/tutorials/email/google-sheets/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/docs/tutorials/email/google-sheets/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: Email to Database | WebhookRelay meta: "og: title": "Email to Database" description: Store every inbound email in your own database. Webhook Relay parses email to JSON and POSTs it to a tiny insert endpoint you run — even one behind a firewall. url: https://webhookrelay.com/docs/tutorials/email/database.md file: /docs/tutorials/email/database.md ---  Documentation **Fundamentals** # **Email to Database** Store every inbound email in your own database. Webhook Relay parses email to JSON and POSTs it to a tiny insert endpoint you run — even one behind a firewall. You want every inbound email stored in **your own database** — an archive, an audit trail, or a queue your app reads from. Doing that the traditional way means running a mail server or polling an IMAP mailbox, parsing raw MIME, and writing a daemon to keep it alive. [Webhook Relay](https://webhookrelay.com) removes all of that. It [receives emails as webhooks](https://webhookrelay.com/docs/tutorials/email/database/docs/email/): you get a unique address, every message sent to it is parsed into JSON, and that JSON is POSTed to a tiny HTTP endpoint you run — which does a single `INSERT`. No mail server, no IMAP loop. ## [How it works](#how-it-works) Webhook Relay doesn't connect to your database directly. It parses the email and POSTs it to an HTTP handler you control, and that handler owns the SQL: ``` inbound email ──▶ Webhook Relay (parse) ──▶ POST ──▶ your insert endpoint ──▶ database ``` The parsed email looks like this: ``` { "from": "jon@example.com", "from_name": "Jon Snow", "recipient": "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/tutorials/email/microsoft-teams/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 `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/tutorials/n8n/email-trigger/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/email-trigger/docs/tutorials/n8n/webhook-trigger/). Did this page help you? --- --- title: Team Member Roles | WebhookRelay meta: "og: title": "Team Member Roles" description: Control what each collaborator can see and do in your Webhook Relay organization with Admin, Billing, Member and Viewer roles. url: https://webhookrelay.com/features/team-member-roles.md file: /features/team-member-roles.md ---  **Plans: Business, Pro and Enterprise** FEATURES # **Team Member Roles** Control what each collaborator can see and do in your Webhook Relay organization with Admin, Billing, Member and Viewer roles.  Team member roles let you grant the right level of access to each person in your organization. Convert your account into an organization, invite colleagues with their own Webhook Relay login, and assign a role that controls resources, billing and membership. For the full overview, see [custom roles](https://webhookrelay.com/features/team-member-roles/features/custom-roles/). ## [Roles](#roles) - **Admin** — full access: members, billing, resources - **Billing** — resources + billing management - **Member** — resources only; no billing or member management - **Viewer** — read-only: sees everything, changes nothing, no billing ## [Why roles matter](#why-roles-matter) - **Least privilege** — give each person exactly the access they need - **Safer onboarding** — invite with a scoped role; revoke when someone leaves - **Billing control** — only Admin and Billing can touch the plan - **Accountability** — pair with [audit logs](https://webhookrelay.com/features/team-member-roles/features/audit-logs/) so every action is attributable Combine with [Single Sign-On (SSO)](https://webhookrelay.com/features/team-member-roles/features/sso/) and [teams](https://webhookrelay.com/features/team-member-roles/features/teams/) for organization-scale webhook management. [Create an account](https://my.webhookrelay.com/register) or [contact sales](https://webhookrelay.com/features/team-member-roles/contact-sales/) to discuss team plans.  ## **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 WhatsApp Cloud API Webhook Setup | WebhookRelay meta: "og: title": "n8n WhatsApp Cloud API Webhook Setup" description: Receive WhatsApp Cloud API webhooks in self-hosted n8n: a stable public URL for Meta, the verify-token handshake answered automatically, no public IP. url: https://webhookrelay.com/docs/tutorials/n8n/whatsapp-cloud-api-webhook.md file: /docs/tutorials/n8n/whatsapp-cloud-api-webhook.md ---  Documentation **Fundamentals** # **n8n WhatsApp Cloud API Webhook Setup** Receive WhatsApp Cloud API webhooks in self-hosted n8n: a stable public URL for Meta, the verify-token handshake answered automatically, no public IP. Meta's WhatsApp Cloud API only delivers webhooks to a **public HTTPS URL**, and before it sends anything it runs a **verification handshake** — a GET request your endpoint must answer by echoing the `hub.challenge` query value. That is two problems for self-hosted n8n: your instance usually is not public, and tunnels with rotating URLs force you to re-verify in the Meta dashboard every time the URL changes. This tutorial solves both with a stable Webhook Relay endpoint: Meta verifies **one permanent URL** (the handshake is answered by a tiny Function, automatically), and your n8n instance receives every message over an **outbound WebSocket** — no public IP, no open ports, nothing to re-verify. ``` Meta ──GET hub.challenge──▶ Webhook Relay (Function answers handshake) Meta ──POST messages──────▶ Webhook Relay (stable public URL) │ n8n ──outbound WebSocket─┘ ← n8n connects out; nothing inbound ``` ## [1. Install the Webhook Relay node in n8n](#_1-install-the-webhook-relay-node-in-n8n) In n8n go to **Settings → Community Nodes → Install** and enter `n8n-nodes-webhookrelay`. Then create an **API key** at [my.webhookrelay.com/tokens](https://my.webhookrelay.com/tokens) and add it as a **Webhook Relay API** credential. (The general setup, with screenshots, is in the [n8n Webhook Trigger tutorial](https://webhookrelay.com/docs/tutorials/n8n/whatsapp-cloud-api-webhook/docs/tutorials/n8n/webhook-trigger/).) ## [2. Create a bucket for WhatsApp](#_2-create-a-bucket-for-whatsapp) In [my.webhookrelay.com](https://my.webhookrelay.com/buckets) create a bucket named `whatsapp`. Its default input URL — `https://xxx.hooks.webhookrelay.com/...` — is permanent. This is the URL Meta will verify once and deliver to forever. ## [3. Answer the verify-token handshake with a Function](#_3-answer-the-verify-token-handshake-with-a-function) Meta's verification GET must be answered with the raw `hub.challenge` value. Attach this Function to the bucket's **input** so the handshake is handled at the edge (n8n never needs to see it): ``` // Answer Meta's one-time subscription verification; let real events through. var VERIFY_TOKEN = "my-verify-token"; // must match what you enter in Meta if (r.RequestMethod() === "GET") { if (r.RequestQuery("hub.verify_token") === VERIFY_TOKEN) { r.SetResponseStatusCode(200); r.SetResponseBody(r.RequestQuery("hub.challenge")); } else { r.SetResponseStatusCode(403); r.SetResponseBody("verification failed"); } } ``` POST deliveries (the actual messages) pass through untouched and get the bucket's normal `200` response, which is all Meta needs. ## [4. Point Meta at the bucket](#_4-point-meta-at-the-bucket) In the [Meta App Dashboard](https://developers.facebook.com/apps/): **WhatsApp → Configuration → Webhook → Edit**. Enter the bucket's input URL as the **Callback URL** and the same verify token as in the Function, then save — verification succeeds instantly. Click **Manage** and subscribe to the **`messages`** webhook field. ## [5. Receive messages in n8n](#_5-receive-messages-in-n8n) Add the **Webhook Relay Trigger** node to a workflow, select the `whatsapp` bucket, and activate. The node opens an outbound WebSocket and every WhatsApp delivery arrives as a workflow execution. Messages sit a few levels deep in Meta's envelope. A **Set** or **Code** node right after the trigger tidies that up: ``` // Code node: flatten the Cloud API envelope into one item per message const out = []; for (const entry of $json.body.entry || []) { for (const change of entry.changes || []) { for (const msg of change.value?.messages || []) { out.push({ json: { from: msg.from, type: msg.type, text: msg.text?.body, timestamp: msg.timestamp, contact: change.value.contacts?.[0]?.profile?.name, }}); } } } return out; ``` Status updates (`sent`/`delivered`/`read`) arrive on the same bucket with a `statuses` array instead of `messages` — filter on what is present. ## [Notes](#notes) - **Restarts are free.** Meta verified the bucket URL, not your n8n instance — redeploy or move n8n anytime, nothing to re-verify. - **Verify signatures if you need authenticity**: Meta signs POSTs with `X-Hub-Signature-256` (HMAC-SHA256 of the raw body with your app secret). The header reaches your workflow intact, so you can check it in a Code node — see [Verify a webhook signature](https://webhookrelay.com/docs/tutorials/n8n/whatsapp-cloud-api-webhook/blog/verify-webhook-signature/). - **Payload reference**: the full setup-and-payload story (including self-hosted gateways like WAHA) is in [WhatsApp Cloud API webhooks: setup, verify token and payloads](https://webhookrelay.com/docs/tutorials/n8n/whatsapp-cloud-api-webhook/blog/whatsapp-cloud-api-webhooks/). Did this page help you? --- --- title: Jenkins Multibranch Pipelines | WebhookRelay meta: "og: title": "Jenkins Multibranch Pipelines" description: Trigger Jenkins Multibranch Pipeline builds from GitHub webhooks without exposing Jenkins — branch and pull request jobs via the Webhook Relay plugin. url: https://webhookrelay.com/docs/tutorials/cicd/jenkins-plugin-multibranch.md file: /docs/tutorials/cicd/jenkins-plugin-multibranch.md ---  Documentation **Fundamentals** # **Jenkins Multibranch Pipelines** Trigger Jenkins Multibranch Pipeline builds from GitHub webhooks without exposing Jenkins — branch and pull request jobs via the Webhook Relay plugin. **Multibranch Pipeline** projects work with the [Webhook Relay Jenkins plugin](https://webhookrelay.com/docs/tutorials/cicd/jenkins-plugin-multibranch/docs/tutorials/cicd/jenkins-plugin/) just like regular jobs — pushes and pull requests on GitHub trigger builds on a Jenkins that has **no public IP**. But they are configured differently from regular jobs, and that trips people up: > **A Multibranch Pipeline has no _Build Triggers_ section.** Don't look for one — nothing is missing from your Jenkins. Branch and pull request jobs are created and triggered by the **branch source** reacting to the webhook events the plugin delivers, with no per-job trigger configuration at all. This page shows the full setup for GitHub. When it's done, every push and pull request travels GitHub → your Webhook Relay bucket → the plugin → `/github-webhook/`, and: - **Push to a branch** — the matching branch job builds. - **Push a new branch** — a job for it is created and built automatically. - **Open a pull request** — a `PR-