Back Up Your n8n Workflows To Github workflow not working?

Are you guys able to get this workflow ( Back Up Your n8n Workflows To Github | n8n workflow template to work? I’m fairly new to n8n. but for the life of me I can’t figure out how to get the “Execute workflow” node to call the embedded subworkflow. Any suggestions?

Information on your n8n setup

  • n8n version: 1.74.1
  • Database (default: SQLite): default
  • n8n EXECUTIONS_PROCESS setting (default: own, main): default
  • Running n8n via (Docker, npm, n8n cloud, desktop app): Docker

Hey @Bob_McCormick

What error are you seeing with it? The execute workflow node should be configured already to call itself so you don’t need to do anything.

This is the same workflow we use internally to back up our workflows every morning at 1am, a few hours ago it ran for us and took ~40 minutes to backup 2600+ workflows.

That’s the odd thing; I wasn’t getting any errors when running the workflow as far as I could tell. I’m new to this, so it’s possible there was something in a log somewhere that I’m just to daft to have seen. :slight_smile: The symptoms I did see is that:

  1. When testing the workflow I’d see the little green checkboxes in the nodes in the main workflow, but never any in the sub workflow.
  2. No files would ever be created in the GitHub repo.

The only error I did see was some “node is out of date” errors. I tried testing the workflow “as is” with the out of date nodes, then re-tried after following the instructions to remove the out of date nodes and re-add new ones. Still no luck.

Not a big deal though. I found this workflow from user @ihortom that works perfectly. I extended it a bit to add Slack notifications similar to the workflow I linked to in my question above. So I’m all good and happy now. :smiley:

Thanks for your quick reply!

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.