Slack Webhook - Verify Signature
Configured with Crypto, Execute Workflow Trigger, Stop And Error. Review the connections and setup before adapting this template.
Node categories in this workflow
- Code
- Transform
- Routing
- Trigger
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 |
|---|---|---|---|
| Make Slack Verif Token | Code | Code | See node parameters |
| Encode Secret String | Transform | Crypto | See node parameters |
| IF | Routing | If | See node parameters |
| Stop and Error | Routing | Stop And Error | See node parameters |
| Execute Workflow Trigger | Trigger | Execute Workflow Trigger | See node parameters |
| Set Verified to True | Transform | Edit Fields | See node parameters |
| Merge | Transform | Merge | 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
Slack Webhook - Verify Signature
Slack Webhook - Verify Signature
When receiving a message from a Slack Webhook, it is much more secure to verify that the message comes from Slack and not from bots or unknown services.
This small template is designed to validate the received signature (See this URL).
Colors
- Blue areas are areas to edit
- Yellow areas are explanations
TO EDIT
TO EDIT
Set your Slack Signing Secret. You can obtain it by visiting your Slack App dashboard in the general tab: https://api.slack.com/apps/[SLACK_APP_ID]/general
Error Output
Error Output
If the signature cannot be verified, an error will be raised. You can manage this scenario in your main workflow by either using an Error Workflow or by modifying your node settings and selecting appropriate actions in the event of an error.
Success Output
Success Output
If the signature is successfully verified, we return a key verified_signature set to true along with the data from the Slack request itself.
Input
Input
The input should be the received Slack request. Place this workflow directly after the Slack Webhook.
Slack Webhook - Verify Signature
Slack Webhook - Verify Signature
Purpose and structure
This folder contains the Slack Webhook - Verify Signature workflow. Its executable nodes use code, crypto, executeWorkflowTrigger, if, merge, set, stopAndError. 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
Execute Workflow Trigger
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/Stopanderror/1164_Stopanderror_Code_Automation_Triggered.json MIT; preserve source notices.