🛠️ Config Node Setup

This node defines the configuration for the secure webhook.

• config.bearerToken: The expected Bearer token for authentication.

• config.requiredFields: Set one key for each required field in the incoming request body (e.g., config.requiredFields.message. 👉 The value doesn't matter, only the keys are checked.

🚫 Error Handling Nodes

These nodes return standardized JSON error responses:

• 🔒 401 Unauthorized: Triggered when the request is missing a valid Bearer token.

• 📭 400 Bad Request: Triggered when required fields are missing from the request body.

✅ Set & 200 Response Nodes

• 🧱 Create Response Builds the JSON response from the incoming request. Use this to extract, transform, or forward specific values (e.g., message, sender, etc.).

• 📬 200 OK Returns a successful response using values from the Create Response node.

🔍 Required Fields Validator

This Code node checks if all fields defined in config.requiredFields are present in the incoming request body.

• Reads the body from the Webhook node.

• Loops through each key in config.requiredFields.

• Returns { valid: true } if all are present, otherwise { valid: false }.

🔐 Secure Webhook – Summary

This workflow protects a public webhook with authentication and payload validation.

---

🧩 Why use it?

• ✅ Ensure only trusted clients can call your workflow (via Bearer token).
• ✅ Validate that all expected fields are present in the request body.
• ✅ Return helpful and consistent JSON responses (200, 400, 401).

---

⚙️ How it works:

1. Webhook – Entry point for external POST requests.
2. Configuration – Defines config.bearerToken and config.requiredFields.
3. Check Authorization Header – Compares incoming Bearer token with config.
4. 401 Unauthorized – Returned if the token is missing or incorrect.
5. Has required fields? – JS code checks for required fields in the request body.
6. 400 Bad Request – Returned if any required field is missing.
7. Create Response & 200 OK – Returns a custom success message.

---

🛠 Setup Instructions:

• Set your desired Bearer token in config.bearerToken.
• For each required field, set a key in config.requiredFields
  (e.g., `config.requiredFields.message). 👉 The value doesn't matter, only the keys are checked.
• Replace the Add workflow nodes here node with your own workflow logic.
• Edit the Create Response node to build your response.

---

📌 Great for building secure, reusable webhook endpoints for APIs, forms, or 3rd-party services.

Support My Work! ❤️

👋 Hello! I'm Audun / xqus 🔗 My work: xqus.com 💸 n8n shop: xqus.gumroad.com

If you find this workflow helpful, consider downloading or purchasing it on Gumroad.

Your support helps me create more useful n8n workflows and resources for the community. -Thanks a lot! 🙌

🚫 Error Handling Nodes

Purpose and structure

This folder contains the 🚫 Error Handling Nodes workflow. Its executable nodes use code, if, noOp, respondToWebhook, set, webhook. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

Webhook

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Code/0922_Code_Webhook_Create_Webhook.json MIT; preserve source notices.