Bear Brown
← All N8N workflows
Messaging & emailCodeExecute WorkflowExecute Workflow TriggerGithubHTTP Request

receive execute workflow events and n8n and http request

Configured with Execute Workflow, Execute Workflow Trigger, Github, HTTP Request, and additional nodes. Review the connections and setup before adapting this template.

Download workflow JSONView files on GitHub ↗23 nodes · MIT
Workflow preview
TriggerOn clicking 'execute'Manual TriggerTriggerExecute WorkflowTriggerExecute Workflow TriggerIntegrationn8nN8NTransformReturnEdit FieldsWeb / APIGet FileHTTP RequestRoutingIf file too largeIfTransformMerge ItemsMergeCodeisDiffOrNewCodeRoutingCheck StatusSwitchRoutingSame file - Do nothingNo OpRoutingFile is differentNo OpRoutingFile is newNo OpIntegrationCreate new fileGithubIntegrationEdit existing fileGithubRoutingLoop Over ItemsLoop Over ItemsTriggerSchedule TriggerSchedule TriggerTransformCreate sub pathEdit FieldsMessagingStarting MessageSlackSubworkflowExecute WorkflowExecute WorkflowMessagingCompleted NotificationSlackMessagingFailed FlowsSlackIntegrationGet file dataGithubTransformConfigEdit Fields

Node categories in this workflow

  • Trigger
  • Integration
  • Transform
  • Web / API
  • Routing
  • Code
  • Messaging
  • Subworkflow

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
On clicking 'execute'TriggerManual TriggerSee node parameters
Execute Workflow TriggerTriggerExecute Workflow TriggerSee node parameters
n8nIntegrationN8NSee node parameters
ReturnTransformEdit FieldsSee node parameters
Get FileWeb / APIHTTP RequestSee node parameters
If file too largeRoutingIfSee node parameters
Merge ItemsTransformMergeSee node parameters
isDiffOrNewCodeCodeSee node parameters
Check StatusRoutingSwitchSee node parameters
Same file - Do nothingRoutingNo OpSee node parameters
File is differentRoutingNo OpSee node parameters
File is newRoutingNo OpSee node parameters
Create new fileIntegrationGithubfile
Edit existing fileIntegrationGithubfile / edit
Loop Over ItemsRoutingLoop Over ItemsSee node parameters
Schedule TriggerTriggerSchedule TriggerSee node parameters
Create sub pathTransformEdit FieldsSee node parameters
Starting MessageMessagingSlackSee node parameters
Execute WorkflowSubworkflowExecute WorkflowSee node parameters
Completed NotificationMessagingSlackSee node parameters
Failed FlowsMessagingSlackSee node parameters
Get file dataIntegrationGithubfile / get
ConfigTransformEdit FieldsSee 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

Backup to GitHub

Backup to GitHub

This workflow will backup all instance workflows to GitHub every 24 hours.

The files are saved into folders using YYYY/MM/ for the directory path and ID.json for the filename.

The Repo Owner, Repo Name and Main folder are set using the Variables feature but can be replaced with the Config node in the subworkflow.

The workflow runs calls itself to help reduce memory usage, Once the workflow has completed it will send an optional notification to Slack.

Time to Run

Tested with 1423 workflows on 1.44.1 it took under 30 minutes for the first run and under 12 minutes once the initial run is complete.

receive execute workflow events and n8n and http request

receive execute workflow events and n8n and http request

Purpose and structure

This folder contains the receive execute workflow events and n8n and http request workflow. Its executable nodes use code, executeWorkflow, executeWorkflowTrigger, github, httpRequest, if, manualTrigger, merge, n8n, noOp, scheduleTrigger, set, slack, splitInBatches, switch. 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

On clicking 'execute', Execute Workflow Trigger, 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/Code/0182_Code_GitHub_Create_Scheduled.json MIT; preserve source notices.

Canvas section labels

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

  • Subworkflow
  • Main workflow loop

More in Messaging & email

Addon for Workflow Nodes Update Check TemplateAge and number of the newsAI Email Filtering Automation