How do I import "0763_Wait_Splitout_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 "0763_Wait_Splitout_Create_Webhook" use?

It uses: executeWorkflow, notion, splitOut, aggregate, httpRequest, wait. The flow diagram above shows how each service connects across the 37 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 executeWorkflow and notion credentials in n8n after import.

What trigger type does "0763_Wait_Splitout_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 "0763_Wait_Splitout_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 executeWorkflow, notion, splitOut, aggregate, httpRequest, wait.

← Workflows

0763_Wait_Splitout_Create_Webhook

37 nodes · executeWorkflow, notion, splitOut, aggregate, httpRequest, wait

Engine: n8n
Nodes: 37
Trigger: scheduled/triggered
Source file: 0763_Wait_Splitout_Create_Webhook.json

Workflow flow

IntegrationsExecuteWorkflow

NotionSplit OutAggregateHTTPWaitIFSet

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

IFExecuteWorkflow

NotionSplit OutSetAggregateHTTPWait

30 steps · use Full diagram for every node

Browse by integration

executeWorkflow notion splitOut aggregate httpRequest wait

Browse all integrations →

Download n8n JSON Download sanitized JSON Download flow graph

Import into n8n

Download the n8n JSON file (full or sanitized).
In n8n: Workflows → Import from file.
Open each node and reconnect credentials to your accounts.
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

0763_Wait_Splitout_Create_Webhook is a free n8n workflow on OpenRuna — 37 nodes connecting executeWorkflow, notion, splitOut, aggregate, httpRequest, wait. Download the JSON, view the flow diagram, and import it into your n8n instance.

What this workflow does

Built in n8n, "0763_Wait_Splitout_Create_Webhook" chains 37 nodes to move data between executeWorkflow, notion, splitOut, aggregate, httpRequest, wait. 37 nodes · executeWorkflow, notion, splitOut, aggregate, httpRequest, wait Execution begins at the scheduled/triggered trigger and flows through the 37 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

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

Example output

Imported into n8n, "0763_Wait_Splitout_Create_Webhook" exposes 37 configured nodes. Trigger type: scheduled/triggered. Integrations: executeWorkflow, notion, splitOut, aggregate, httpRequest, wait. Open each node after import to map credentials to your own executeWorkflow and notion 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 "0763_Wait_Splitout_Create_Webhook" JSON into a plain-English runbook, node by node. It can flag where executeWorkflow 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 executeWorkflow, notion, splitOut, aggregate, httpRequest, wait. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "0763_Wait_Splitout_Create_Webhook" — extract executeWorkflow IDs and secrets into environment variables without changing the 37-node structure.

Frequently asked questions

How do I import "0763_Wait_Splitout_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 "0763_Wait_Splitout_Create_Webhook" use?: It uses: executeWorkflow, notion, splitOut, aggregate, httpRequest, wait. The flow diagram above shows how each service connects across the 37 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 executeWorkflow and notion credentials in n8n after import.
What trigger type does "0763_Wait_Splitout_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 "0763_Wait_Splitout_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 executeWorkflow, notion, splitOut, aggregate, httpRequest, wait.