OpenRuna
Sign in
← Workflows

Retry Execution Hourly

13 nodes · manual, n8n, httpRequest, splitInBatches, schedule

Engine
n8n
Nodes
13
Trigger
scheduled/triggered
Source file
1524_Schedule_Manual_Automation_Scheduled.json

Workflow flow

IntegrationsManualN8NHTTPSplitInBatchesScheduleIFNoOpSet
100%
TRIGGER

When clicking ‘Test workflow’

Manual

retry workflow automatically

HTTP

TRIGGER

Schedule Trigger

Schedule

login_details

Set

Log into n8n

HTTP

n8n

N8N

If

IF

No Operation, do nothing

NoOp

Loop Over Items

SplitInBatches

9 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: Retry Execution Hourly. 13 nodes across manual, n8n, httpRequest, splitInBatches, schedule, with a downloadable JSON and a visual flow diagram on OpenRuna.

What this workflow does

"Retry Execution Hourly" automates a manual-to-n8n flow in n8n across 13 nodes. 13 nodes · manual, n8n, httpRequest, splitInBatches, schedule 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

  • Study how data moves from manual to n8n before building your own variant.
  • Use it as a starting template when wiring manual, n8n, httpRequest, splitInBatches, schedule — adjust node parameters to your accounts and record IDs.
  • Import "Retry Execution Hourly" into n8n, reconnect credentials for manual, n8n, httpRequest, splitInBatches, schedule, and run the same automation in your own workspace.
  • Benchmark it against your current manual integration to spot missing steps or redundant nodes.

Example output

Imported into n8n, "Retry Execution Hourly" exposes 13 configured nodes. Trigger type: scheduled/triggered. Integrations: manual, n8n, httpRequest, splitInBatches, schedule. Set your credentials on the manual 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 "Retry Execution Hourly" into Claude and ask it to explain each of the 13 nodes. Claude is good at suggesting credential mappings for manual, n8n, httpRequest, splitInBatches, schedule, plus error-handling and idempotency improvements before you run it in production.

ChatGPT

Have ChatGPT generate a checklist for adapting "Retry Execution Hourly" to your accounts — which manual, n8n, httpRequest, splitInBatches, schedule 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 13 nodes.

Frequently asked questions

How do I import "Retry Execution Hourly" 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 "Retry Execution Hourly" use?
It uses: manual, n8n, httpRequest, splitInBatches, schedule. The flow diagram above shows how each service connects across the 13 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 n8n credentials in n8n after import.
What trigger type does "Retry Execution Hourly" 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 "Retry Execution Hourly" 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, n8n, httpRequest, splitInBatches, schedule.

Related resources