Monitor backup and sync logs with Google Cloud Storage, GitHub, Gmail, OpenAI, and GLPI
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 AI workflow has 22 nodes and runs on a schedule (every day). Along the way it connects Google Cloud Storage, Gmail, GitHub and OpenAI.
How it runs
Trigger: On a schedule (every day).
- Set_Context (Edit Fields (Set)): sets or maps fields
- Set_Prefix (Edit Fields (Set)): sets or maps fields
- Get a list of objects (Google Cloud Storage): uses Google Cloud Storage
- Bucket _ Download Log (Google Cloud Storage): uses Google Cloud Storage
- GitHub: uses GitHub
- Exclude OneDrive Logs (If): checks a condition and branches into true / false
- Loop: (Loop Over Items (Split in Batches)): loops over the items in batches
- Code: runs custom JavaScript code
- Loop: (Loop Over Items (Split in Batches)): loops over the items in batches
- Code: runs custom JavaScript code
…plus 11 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 (11)
- Google Cloud Storage
n8n-nodes-base.googleCloudStorage - Code
n8n-nodes-base.code - Edit Fields (Set)
n8n-nodes-base.set - Gmail
n8n-nodes-base.gmail - Schedule Trigger
n8n-nodes-base.scheduleTrigger - If
n8n-nodes-base.if - GitHub
n8n-nodes-base.github - HTTP Request
n8n-nodes-base.httpRequest - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - Switch
n8n-nodes-base.switch - OpenAI
@n8n/n8n-nodes-langchain.openAi
From the author
Quick overview Monitor backup and synchronization jobs by validating structured execution logs rather than remotely executing the jobs. The workflow checks expected daily evidence, identifies missing or failed runs, and can route operational alerts through…