execute workflow and receive schedule events and get redis
Configured with Execute Workflow, Filter, Redis, Schedule Trigger. Review the connections and setup before adapting this template.
Node categories in this workflow
- Subworkflow
- Trigger
- Data store
- Routing
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.
| Node | Category | Type | Operation |
|---|---|---|---|
| Execute Workflow | Subworkflow | Execute Workflow | See node parameters |
| Schedule Trigger | Trigger | Schedule Trigger | See node parameters |
| Get Status | Data store | Redis | get |
| Set Running | Data store | Redis | set |
| Set Idle | Data store | Redis | set |
| Continue if Idle | Routing | Filter | See node parameters |
| Redis Key exists | Routing | If | See node parameters |
| No Operation | Routing | No Op | See node parameters |
| When clicking "Test workflow" | Trigger | Manual Trigger | See node parameters |
| Reset to Idle | Data store | Redis | set |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- 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
redis
Workflow notes
Troubleshooting
Troubleshooting
Unplanned server outage? Need to reset the flag? Disable the schedule trigger, activate these nodes and run the Reset to Idle node manually.
Sticky Note1
This updates the flag, indicating, that the workflow is currently running
Set Interval
Set Interval
Define how frequently the main workflow should run.
Sticky Note3
If the flag stored in Redis already exists and indicates, that the worklow is still running, another execution will be prevented. In that case this workflow ends here.
Set Workflow ID
Set Workflow ID
Set the ID of the main workflow which should be executed
Sticky Note5
This checks for a dynamic flag (containing the workflow ID) which represents if the workflow is currently running.
Sticky Note6
This updates the flag, indicating, that the workflow is currently idle
execute workflow and receive schedule events and get redis
execute workflow and receive schedule events and get redis
Purpose and structure
This folder contains the execute workflow and receive schedule events and get redis workflow. Its executable nodes use executeWorkflow, filter, if, manualTrigger, noOp, redis, scheduleTrigger. 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
Schedule Trigger, When clicking "Test workflow"
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/Redis/0497_Redis_Schedule_Import_Scheduled.json MIT; preserve source notices.