← All N8N workflows
Automation & utilitiesHTTP RequestIfManual TriggerN8NNo Op

Retry Execution Hourly

Configured with HTTP Request, N8N, Schedule Trigger, Loop Over Items. Review the connections and setup before adapting this template.

Workflow preview
TriggerWhen clicking ‘Testworkflow’Manual TriggerIntegrationn8nN8NWeb / APILog into n8nHTTP RequestWeb / APIretry workflowautomaticallyHTTP RequestRoutingIfIfRoutingNo Operation, donothingNo OpTransformlogin_detailsEdit FieldsRoutingLoop Over ItemsLoop Over ItemsTriggerSchedule TriggerSchedule Trigger

Node categories in this workflow

  • Trigger
  • Integration
  • Web / API
  • Routing
  • Transform

Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.

Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.

How it works

The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.

Workflow node names, types, and operations
NodeCategoryTypeOperation
When clicking ‘Test workflow’TriggerManual TriggerSee node parameters
n8nIntegrationN8Nexecution
Log into n8nWeb / APIHTTP RequestPOST
retry workflow automaticallyWeb / APIHTTP RequestPOST
IfRoutingIfSee node parameters
No Operation, do nothingRoutingNo OpSee node parameters
login_detailsTransformEdit FieldsSee node parameters
Loop Over ItemsRoutingLoop Over ItemsSee node parameters
Schedule TriggerTriggerSchedule TriggerSee node parameters

Setup

  1. Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
  2. Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
  3. Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
  4. Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.

Requirements

An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.

Credential types declared in the source

  • n8nApi

Workflow notes

Sticky Note
  • check for failed executions hourly.

  • filter out those that have successful reexecution ids.

  • log into n8n and get the session ids.

  • retry the executions.

  • h

Get all `Error` executions.

Get all Error executions.

  • Filter out those that have been successfully retried

Retry the executions.

Retry the executions.

  • Feel free to add notifications error messages for failed one to email or slack

Retry Execution Hourly

Retry Execution Hourly

Purpose and structure

This folder contains the Retry Execution Hourly workflow. Its executable nodes use httpRequest, if, manualTrigger, n8n, noOp, scheduleTrigger, set, splitInBatches. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

When clicking ‘Test workflow’, Schedule Trigger

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Schedule/1524_Schedule_Manual_Automation_Scheduled.json MIT; preserve source notices.

Canvas section labels

These name areas of the original canvas; they do not include explanatory instructions.

  • Set the login credential details in the set node, and login to n8n via api.

More in Automation & utilities