Validate Seatable Webhooks with HMAC SHA256 Authentication
Configured with Crypto, Respond To Webhook, Webhook. Review the connections and setup before adapting this template.
Node categories in this workflow
- Web / API
- Transform
- Trigger
- Routing
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| 200 | Web / API | Respond To Webhook | See node parameters |
| 403 | Web / API | Respond To Webhook | See node parameters |
| Calculate sha256 | Transform | Crypto | See node parameters |
| Seatable Webhook | Trigger | Webhook | See node parameters |
| Add nodes for processing | Routing | No Op | See node parameters |
| hash matches | Routing | If | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
None declared. HTTP requests and Code nodes may still need configuration.
Workflow notes
📌 Validate Seatable Webhooks with HMAC SHA256 Authentication
📌 Validate Seatable Webhooks with HMAC SHA256 Authentication
This mini workflow is designed to securely validate incoming Seatable webhooks using HMAC SHA256 signature verification.
🔐 What it does:
- Listens for incoming Seatable webhook requests.
- Calculates a SHA256 HMAC hash of the raw request body using your shared secret.
- Compares the computed hash with the
x-seatable-signatureheader (after removing thesha256=prefix). - If the hashes match: responds with 200 OK and forwards the request to subsequent nodes.
- If the hashes don’t match: responds with 403 Forbidden.
⚠️ Important Notes:
This workflow is provided as a template and is not intended to work standalone. Please duplicate it and integrate it with your custom logic at the "Add nodes for processing" node.
Configuration steps:
- Set your secret key in the “Calculate sha256” crypto node (replace the placeholder).
- Adjust the webhook path to suit your environment (or set it to "manual" for testing).
- Connect your actual logic after the verification step.
Validate Seatable Webhooks with HMAC SHA256 Authentication
Validate Seatable Webhooks with HMAC SHA256 Authentication
Purpose and structure
This folder contains the Validate Seatable Webhooks with HMAC SHA256 Authentication workflow. Its executable nodes use crypto, if, noOp, respondToWebhook, 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
Seatable 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/Webhook/1740_Webhook_Respondtowebhook_Automation_Webhook.json MIT; preserve source notices.