WordPress context backup to github
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 21 nodes and runs manually, when you click “Execute workflow” (plus 2 other triggers). Along the way it connects GitHub and Wordpress.
How it runs
Trigger: Manually, when you click “Execute workflow” (plus 2 other triggers).
- Get All WP Posts (Wordpress): get many
- Merge: merges the data from its input branches
- tag? (Switch): routes items into 2 branches
- Format JSON (Code): runs custom JavaScript code
- isDiffOrNew (Code): runs custom JavaScript code
- / (Edit Fields (Set)): sets 1 field: tags[0].name
- Globals (Edit Fields (Set)): sets 3 fields: repo.owner, repo.name, repo.path
- Execute Workflow (Execute Sub-workflow): calls another n8n workflow
- Check Status (Switch): routes items into 3 branches
- Get file data (GitHub): get (file)
…plus 5 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (13)
- Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest - If
n8n-nodes-base.if - Merge
n8n-nodes-base.merge - Code
n8n-nodes-base.code - Switch
n8n-nodes-base.switch - No Operation, do nothing
n8n-nodes-base.noOp - GitHub
n8n-nodes-base.github - Execute Workflow Trigger
n8n-nodes-base.executeWorkflowTrigger - Manual Trigger
n8n-nodes-base.manualTrigger - Wordpress
n8n-nodes-base.wordpress - Execute Sub-workflow
n8n-nodes-base.executeWorkflow - Schedule Trigger
n8n-nodes-base.scheduleTrigger
From the author
This template can backup WordPress context github。