OpenRuna
Sign in
← Workflows

Slack Webhook - Verify Signature

12 nodes · crypto, stopAndError, executeWorkflow

Engine
n8n
Nodes
12
Trigger
scheduled/triggered
Source file
1164_Stopanderror_Code_Automation_Triggered.json

Workflow flow

IntegrationsCryptoStopAndErrorExecuteWorkflowCodeIFSetMerge
100%
TRIGGER

Execute Workflow Trigger

ExecuteWorkflow

Make Slack Verif Token

Code

Encode Secret String

Crypto

IF

IF

Stop and Error

StopAndError

Set Verified to True

Set

Merge

Merge

7 steps · flows top to bottom, branches left to right

Browse by integration

Browse all integrations →

Import into n8n

  1. Download the n8n JSON file (full or sanitized).
  2. In n8n: Workflows → Import from file.
  3. Open each node and reconnect credentials to your accounts.
  4. Test with manual execution before enabling triggers.

Sanitized JSON removes credential IDs — safer for sharing. Flow graph JSON is OpenRuna's lightweight format for diagrams and other tools, not n8n import.

View source corpus ↗

Overview

Slack Webhook - Verify Signature (12-node n8n automation, crypto, stopAndError, executeWorkflow) is free on OpenRuna — view the graph and export the JSON to import into n8n.

What this workflow does

"Slack Webhook - Verify Signature" automates a crypto-to-stopAndError flow in n8n across 12 nodes. 12 nodes · crypto, stopAndError, executeWorkflow Execution begins at the scheduled/triggered trigger and flows through the 12 configured nodes. On OpenRuna you get the visual graph, the integration list, and a downloadable JSON ready to import into n8n. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

  • Benchmark it against your current crypto integration to spot missing steps or redundant nodes.
  • Fork it to add error handling, retries, or a notification step without designing the 12-node flow from scratch.
  • Share it with your team as a documented reference for scheduled/triggered automations in the crypto stack.
  • Study how data moves from crypto to stopAndError before building your own variant.

Example output

Imported into n8n, "Slack Webhook - Verify Signature" exposes 12 configured nodes. Trigger type: scheduled/triggered. Integrations: crypto, stopAndError, executeWorkflow. Open each node after import to map credentials to your own crypto and stopAndError accounts. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Paste the exported JSON for "Slack Webhook - Verify Signature" into Claude and ask it to explain each of the 12 nodes. Claude is good at suggesting credential mappings for crypto, stopAndError, executeWorkflow, plus error-handling and idempotency improvements before you run it in production.

ChatGPT

Have ChatGPT generate a checklist for adapting "Slack Webhook - Verify Signature" to your accounts — which crypto, stopAndError, executeWorkflow credentials to create and which node parameters to change first.

Cursor

Open the downloaded JSON in Cursor and use Agent mode to refactor hard-coded URLs into env vars, or to generate tests for any Code nodes. Keep the OpenRuna flow diagram open so you do not break connection order across the 12 nodes.

Frequently asked questions

How do I import "Slack Webhook - Verify Signature" into n8n?
Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.
Which integrations does "Slack Webhook - Verify Signature" use?
It uses: crypto, stopAndError, executeWorkflow. The flow diagram above shows how each service connects across the 12 nodes. Filter OpenRuna by integration to find related workflows and tools.
Can I import a sanitized export without credentials?
Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own crypto and stopAndError credentials in n8n after import.
What trigger type does "Slack Webhook - Verify Signature" use?
Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.
Is "Slack Webhook - Verify Signature" free to use?
OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for crypto, stopAndError, executeWorkflow.

Related resources