OpenRuna
Sign in
← Workflows

0716_Wait_Webhook_Process_Webhook

23 nodes · manual, wait, httpRequest, webhook, respondToWebhook

Engine
n8n
Nodes
23
Trigger
scheduled/triggered
Source file
0716_Wait_Webhook_Process_Webhook.json

Workflow flow

IntegrationsManualWaitHTTPWebhookRespondToWebhookSet
100%
TRIGGER

When clicking ‘Test workflow’

Manual

TRIGGER

Receive Input from External, Independent Process

Webhook

TRIGGER

Webhook

Webhook

HTTP Request - Resume Other Workflow Execution

HTTP

Set Primary Execution Context

Set

Respond to Webhook

RespondToWebhook

HTTP Request - Initiate Independent Process

HTTP

Demo "Trigger" Callback Setup

Set

Wait

Wait

HTTP Request - Get A Random Joke

HTTP

This Node Can Access Primary and Secondary

Set

Simulate some Consumed Service Time

Wait

Simulate Event that Hits the 2nd Trigger/Flow

HTTP

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

Browse by integration

manualwaithttpRequestwebhookrespondToWebhook
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: 0716_Wait_Webhook_Process_Webhook. 23 nodes across manual, wait, httpRequest, webhook, respondToWebhook, with a downloadable JSON and a visual flow diagram on OpenRuna.

What this workflow does

This n8n workflow, "0716_Wait_Webhook_Process_Webhook", wires together manual, wait, httpRequest, webhook, respondToWebhook in 23 nodes. 23 nodes · manual, wait, httpRequest, webhook, respondToWebhook It starts from a scheduled/triggered trigger and routes data through every node in order. 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

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

Example output

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

Cursor

In Cursor, ask Agent mode to parameterise "0716_Wait_Webhook_Process_Webhook" — extract manual IDs and secrets into environment variables without changing the 23-node structure.

Frequently asked questions

How do I import "0716_Wait_Webhook_Process_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 "0716_Wait_Webhook_Process_Webhook" use?
It uses: manual, wait, httpRequest, webhook, respondToWebhook. The flow diagram above shows how each service connects across the 23 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 manual and wait credentials in n8n after import.
What trigger type does "0716_Wait_Webhook_Process_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 "0716_Wait_Webhook_Process_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 manual, wait, httpRequest, webhook, respondToWebhook.

Related resources