OpenRuna
Sign in
← Workflows

0878_HTTP_Aggregate_Import_Webhook

20 nodes · executeWorkflow, switch, toolWorkflow, httpRequest, aggregate, mcp

Engine
n8n
Nodes
20
Trigger
scheduled/triggered
Source file
0878_HTTP_Aggregate_Import_Webhook.json

Workflow flow

IntegrationsExecuteWorkflowSwitchToolWorkflowHTTPAggregateMCP@n8n/n8n-nodes-langchain.toolWorkflowSet@n8n/n8n-nodes-langchain.mcp
100%
TRIGGER

When Executed by Another Workflow

ExecuteWorkflow

Youtube Transcripts

@n8n/n8n-nodes-langchain.toolWorkflow

Youtube Search

@n8n/n8n-nodes-langchain.toolWorkflow

Usage Report

@n8n/n8n-nodes-langchain.toolWorkflow

TRIGGER

Apify Youtube MCP Server

@n8n/n8n-nodes-langchain.mcp

Operation

Switch

Apify Youtube Search

HTTP

Apify Youtube Transcripts

HTTP

Get Usage Metrics

HTTP

Simplify Search Results

Set

Simplify Transcript Results

Set

Get Usage Limits

HTTP

Aggregate Search Results

Aggregate

Aggregate Transcript Results

Aggregate

Simplify Usage Metrics

Set

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

Browse by integration

executeWorkflowswitchtoolWorkflowhttpRequestaggregatemcp
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

0878_HTTP_Aggregate_Import_Webhook is a free n8n workflow on OpenRuna — 20 nodes connecting executeWorkflow, switch, toolWorkflow, httpRequest, aggregate, mcp. Download the JSON, view the flow diagram, and import it into your n8n instance.

What this workflow does

This n8n workflow, "0878_HTTP_Aggregate_Import_Webhook", wires together executeWorkflow, switch, toolWorkflow, httpRequest, aggregate, mcp in 20 nodes. 20 nodes · executeWorkflow, switch, toolWorkflow, httpRequest, aggregate, mcp It starts from a scheduled/triggered trigger and routes data through every node in order. OpenRuna shows the full flow diagram, an integration breakdown, and a one-click JSON export for n8n's "Import from file". Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

  • Import "0878_HTTP_Aggregate_Import_Webhook" into n8n, reconnect credentials for executeWorkflow, switch, toolWorkflow, httpRequest, aggregate, mcp, and run the same automation in your own workspace.
  • Use it as a starting template when wiring executeWorkflow, switch, toolWorkflow, httpRequest, aggregate, mcp — adjust node parameters to your accounts and record IDs.
  • Study how data moves from executeWorkflow to switch 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, "0878_HTTP_Aggregate_Import_Webhook" exposes 20 configured nodes. Trigger type: scheduled/triggered. Integrations: executeWorkflow, switch, toolWorkflow, httpRequest, aggregate, mcp. Open each node after import to map credentials to your own executeWorkflow and switch 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 "0878_HTTP_Aggregate_Import_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, switch, toolWorkflow, httpRequest, aggregate, mcp. Handy for onboarding teammates new to n8n.

Cursor

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

Frequently asked questions

How do I import "0878_HTTP_Aggregate_Import_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 "0878_HTTP_Aggregate_Import_Webhook" use?
It uses: executeWorkflow, switch, toolWorkflow, httpRequest, aggregate, mcp. The flow diagram above shows how each service connects across the 20 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 switch credentials in n8n after import.
What trigger type does "0878_HTTP_Aggregate_Import_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 "0878_HTTP_Aggregate_Import_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, switch, toolWorkflow, httpRequest, aggregate, mcp.

Related resources