OpenRuna
Sign in
← Workflows

0644_Webhook_Slack_Create_Webhook

63 nodes · theHiveProject, httpRequest, slack, respondToWebhook, switch, webhook

Engine
n8n
Nodes
63
Trigger
scheduled/triggered
Source file
0644_Webhook_Slack_Create_Webhook.json

Workflow flow

IntegrationsTheHiveProjectHTTPSlackRespondToWebhookSwitchWebhookSetIFNoOp

Integration path in execution order (sticky notes and duplicate steps omitted)

TheHiveProjectSetHTTPIFNoOpSlackRespondToWebhookSwitchWebhook

45 steps · use Full diagram for every node

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

0644_Webhook_Slack_Create_Webhook (63-node n8n automation, theHiveProject, httpRequest, slack, respondToWebhook, switch, webhook) is free on OpenRuna — view the graph and export the JSON to import into n8n.

What this workflow does

Built in n8n, "0644_Webhook_Slack_Create_Webhook" chains 63 nodes to move data between theHiveProject, httpRequest, slack, respondToWebhook, switch, webhook. 63 nodes · theHiveProject, httpRequest, slack, respondToWebhook, switch, webhook A scheduled/triggered entry point kicks it off, and each node passes data to the next until the run completes. OpenRuna renders the node graph and offers the JSON export so you can import and adapt it in minutes. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

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

Example output

Imported into n8n, "0644_Webhook_Slack_Create_Webhook" exposes 63 configured nodes. Trigger type: scheduled/triggered. Integrations: theHiveProject, httpRequest, slack, respondToWebhook, switch, webhook. Reconnect the theHiveProject credential first, then walk the remaining nodes top to bottom. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Ask Claude to turn the "0644_Webhook_Slack_Create_Webhook" JSON into a plain-English runbook, node by node. It can flag where theHiveProject rate limits or missing retries might bite before you go live.

ChatGPT

Drop the workflow JSON or this OpenRuna page URL into ChatGPT and ask for a step-by-step runbook: triggers, branches, and which fields to customise for theHiveProject, httpRequest, slack, respondToWebhook, switch, webhook. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "0644_Webhook_Slack_Create_Webhook" — extract theHiveProject IDs and secrets into environment variables without changing the 63-node structure.

Frequently asked questions

How do I import "0644_Webhook_Slack_Create_Webhook" 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 "0644_Webhook_Slack_Create_Webhook" use?
It uses: theHiveProject, httpRequest, slack, respondToWebhook, switch, webhook. The flow diagram above shows how each service connects across the 63 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 theHiveProject and httpRequest credentials in n8n after import.
What trigger type does "0644_Webhook_Slack_Create_Webhook" 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 "0644_Webhook_Slack_Create_Webhook" 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 theHiveProject, httpRequest, slack, respondToWebhook, switch, webhook.

Related resources