OpenRuna
Sign in
← Workflows

0826_Wait_Splitout_Automation_Webhook

39 nodes · httpRequest, executeWorkflow, wait, manual, aggregate, memoryBufferWindow

Engine
n8n
Nodes
39
Trigger
scheduled/triggered
Source file
0826_Wait_Splitout_Automation_Webhook.json

Workflow flow

IntegrationsHTTPExecuteWorkflowWaitManualAggregateMemoryBufferWindowMemoryManagerExecutionDataSplit OutFilterCodeIF+4 more
100%
TRIGGER

When Executed by Another Workflow

ExecuteWorkflow

TRIGGER

Run example

Manual

Simple Memory Store

@n8n/n8n-nodes-langchain.memoryBufferWindow

Submit batch

HTTP

One query example

Set

Truncate Chat Memory

@n8n/n8n-nodes-langchain.memoryManager

Fill Chat Memory with example data

@n8n/n8n-nodes-langchain.memoryManager

Append execution data for single query example

Set

Build batch 'request' object for single query

Code

Load Chat Memory Data

@n8n/n8n-nodes-langchain.memoryManager

Delete original properties

Set

Append execution data for chat memory example

Set

Build batch 'request' object from Chat Memory and execution data

Code

Join two example requests into array

Merge

Construct 'requests' array

Aggregate

Set desired 'anthropic-version'

Set

Execute Workflow 'Process Multiple Prompts in Parallel with Anthropic Claude Batch API'

ExecuteWorkflow

Filter Second Prompt Results

Filter

Filter First Prompt Results

Filter

First Prompt Result

ExecutionData

Second Prompt Result

ExecutionData

Get results

HTTP

Batch Status Poll Interval

Wait

Check batch status

HTTP

Parse response

Code

If ended processing

IF

Split Out Parsed Results

Split Out

27 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

Free n8n workflow: 0826_Wait_Splitout_Automation_Webhook. 39 nodes across httpRequest, executeWorkflow, wait, manual, aggregate, memoryBufferWindow, memoryManager, executionData, with a downloadable JSON and a visual flow diagram on OpenRuna.

What this workflow does

"0826_Wait_Splitout_Automation_Webhook" automates a httpRequest-to-executeWorkflow flow in n8n across 39 nodes. 39 nodes · httpRequest, executeWorkflow, wait, manual, aggregate, memoryBufferWindow It starts from a scheduled/triggered trigger and routes data through every node in order. 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 httpRequest integration to spot missing steps or redundant nodes.
  • Fork it to add error handling, retries, or a notification step without designing the 39-node flow from scratch.
  • Share it with your team as a documented reference for scheduled/triggered automations in the httpRequest stack.
  • Study how data moves from httpRequest to executeWorkflow before building your own variant.

Example output

Imported into n8n, "0826_Wait_Splitout_Automation_Webhook" exposes 39 configured nodes. Trigger type: scheduled/triggered. Integrations: httpRequest, executeWorkflow, wait, manual, aggregate, memoryBufferWindow, memoryManager, executionData. Set your credentials on the httpRequest node, then verify each downstream node picks them up. 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 "0826_Wait_Splitout_Automation_Webhook" into Claude and ask it to explain each of the 39 nodes. Claude is good at suggesting credential mappings for httpRequest, executeWorkflow, wait, manual, aggregate, memoryBufferWindow, memoryManager, executionData, plus error-handling and idempotency improvements before you run it in production.

ChatGPT

Have ChatGPT generate a checklist for adapting "0826_Wait_Splitout_Automation_Webhook" to your accounts — which httpRequest, executeWorkflow, wait, manual, aggregate, memoryBufferWindow, memoryManager, executionData 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 39 nodes.

Frequently asked questions

How do I import "0826_Wait_Splitout_Automation_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 "0826_Wait_Splitout_Automation_Webhook" use?
It uses: httpRequest, executeWorkflow, wait, manual, aggregate, memoryBufferWindow, memoryManager, executionData. The flow diagram above shows how each service connects across the 39 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 executeWorkflow credentials in n8n after import.
What trigger type does "0826_Wait_Splitout_Automation_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 "0826_Wait_Splitout_Automation_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, executeWorkflow, wait, manual, aggregate, memoryBufferWindow, memoryManager, executionData.

Related resources