OpenRuna
Sign in
← Workflows

0620_Wait_Slack_Automate_Webhook

28 nodes · httpRequest, xml, splitInBatches, wait, executeWorkflow, slack

Engine
n8n
Nodes
28
Trigger
scheduled/triggered
Source file
0620_Wait_Slack_Automate_Webhook.json

Workflow flow

IntegrationsHTTPXMLSplitInBatchesWaitExecuteWorkflowSlackManualIFSetMergeNoOp
100%
TRIGGER

Execute Workflow Trigger

ExecuteWorkflow

TRIGGER

When clicking "Test workflow"

Manual

Demo Data

Set

Global Variables & Slack Channel

Set

Post Receipt

Slack

Save receipt message timestamp

Set

Merge

Merge

Start VM Scan in Qualys

HTTP

Convert XML to JSON

XML

Confirm Waiting

Slack

Begin Wait Loop

NoOp

Merge1

Merge

Fetch Scan Results

HTTP

Loop Over Items

SplitInBatches

Convert XML to JSON1

XML

Delete Receipt

Slack

Post Vulnerability Scan Summary to Slack

Slack

Wait 5 Min

Wait

Check if Scan Finished

IF

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

Browse by integration

httpRequestxmlsplitInBatcheswaitexecuteWorkflowslackmanual
Browse all integrations →
Download n8n JSONDownload sanitized JSONDownload flow graph

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

Free n8n workflow: 0620_Wait_Slack_Automate_Webhook. 28 nodes across httpRequest, xml, splitInBatches, wait, executeWorkflow, slack, manual, with a downloadable JSON and a visual flow diagram on OpenRuna.

What this workflow does

Built in n8n, "0620_Wait_Slack_Automate_Webhook" chains 28 nodes to move data between httpRequest, xml, splitInBatches, wait, executeWorkflow, slack, manual. 28 nodes · httpRequest, xml, splitInBatches, wait, executeWorkflow, slack 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

  • Study how data moves from httpRequest to xml before building your own variant.
  • Share it with your team as a documented reference for scheduled/triggered automations in the httpRequest stack.
  • Import "0620_Wait_Slack_Automate_Webhook" into n8n, reconnect credentials for httpRequest, xml, splitInBatches, wait, executeWorkflow, slack, manual, and run the same automation in your own workspace.
  • Use it as a starting template when wiring httpRequest, xml, splitInBatches, wait, executeWorkflow, slack, manual — adjust node parameters to your accounts and record IDs.

Example output

Imported into n8n, "0620_Wait_Slack_Automate_Webhook" exposes 28 configured nodes. Trigger type: scheduled/triggered. Integrations: httpRequest, xml, splitInBatches, wait, executeWorkflow, slack, manual. Open each node after import to map credentials to your own httpRequest and xml accounts. 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 "0620_Wait_Slack_Automate_Webhook" JSON into a plain-English runbook, node by node. It can flag where httpRequest 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 httpRequest, xml, splitInBatches, wait, executeWorkflow, slack, manual. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "0620_Wait_Slack_Automate_Webhook" — extract httpRequest IDs and secrets into environment variables without changing the 28-node structure.

Frequently asked questions

How do I import "0620_Wait_Slack_Automate_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 "0620_Wait_Slack_Automate_Webhook" use?
It uses: httpRequest, xml, splitInBatches, wait, executeWorkflow, slack, manual. The flow diagram above shows how each service connects across the 28 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 httpRequest and xml credentials in n8n after import.
What trigger type does "0620_Wait_Slack_Automate_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 "0620_Wait_Slack_Automate_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 httpRequest, xml, splitInBatches, wait, executeWorkflow, slack, manual.

Related resources