OpenRuna
Sign in
← Workflows

Google Site Index - sitemap.xml example

21 nodes · manual, splitOut, httpRequest, splitInBatches, wait, schedule

Engine
n8n
Nodes
21
Trigger
scheduled/triggered
Source file
1145_Wait_Splitout_Automation_Webhook.json

Workflow flow

IntegrationsManualSplit OutHTTPSplitInBatchesWaitScheduleXMLSortIFSet
100%
TRIGGER

When clicking "Test workflow"

Manual

TRIGGER

Schedule Trigger

Schedule

Get sitemap.xml

HTTP

Convert sitemap to JSON

XML

Get content-specific sitemaps

Split Out

Get content of each sitemap

HTTP

convert page data to JSON

XML

Force urlset.url to array

Set

Split Out

Split Out

Sort

Sort

Assign mandatiry sitemap fields

Set

Check status

HTTP

is new?

IF

URL Updated

HTTP

Wait

Wait

Loop Over Items

SplitInBatches

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

Browse by integration

manualsplitOuthttpRequestsplitInBatcheswaitschedulexmlsort
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

Google Site Index - sitemap.xml example (21-node n8n automation, manual, splitOut, httpRequest, splitInBatches, wait, schedule, xml, sort) is free on OpenRuna — view the graph and export the JSON to import into n8n.

What this workflow does

Built in n8n, "Google Site Index - sitemap.xml example" chains 21 nodes to move data between manual, splitOut, httpRequest, splitInBatches, wait, schedule, xml, sort. 21 nodes · manual, splitOut, httpRequest, splitInBatches, wait, schedule Execution begins at the scheduled/triggered trigger and flows through the 21 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

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

Example output

Imported into n8n, "Google Site Index - sitemap.xml example" exposes 21 configured nodes. Trigger type: scheduled/triggered. Integrations: manual, splitOut, httpRequest, splitInBatches, wait, schedule, xml, sort. Open each node after import to map credentials to your own manual and splitOut 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 "Google Site Index - sitemap.xml example" 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, splitOut, httpRequest, splitInBatches, wait, schedule, xml, sort. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "Google Site Index - sitemap.xml example" — extract manual IDs and secrets into environment variables without changing the 21-node structure.

Frequently asked questions

How do I import "Google Site Index - sitemap.xml example" 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 "Google Site Index - sitemap.xml example" use?
It uses: manual, splitOut, httpRequest, splitInBatches, wait, schedule, xml, sort. The flow diagram above shows how each service connects across the 21 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 splitOut credentials in n8n after import.
What trigger type does "Google Site Index - sitemap.xml example" 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 "Google Site Index - sitemap.xml example" 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, splitOut, httpRequest, splitInBatches, wait, schedule, xml, sort.

Related resources