Backup Clockify to Github based on monthly reports
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.
Nodes used (11)
- Extract from File
n8n-nodes-base.extractFromFile - Compare Datasets
n8n-nodes-base.compareDatasets - Stop and Error
n8n-nodes-base.stopAndError - Edit Fields (Set)
n8n-nodes-base.set - Split Out
n8n-nodes-base.splitOut - Filter
n8n-nodes-base.filter - Clockify
n8n-nodes-base.clockify - HTTP Request
n8n-nodes-base.httpRequest - GitHub
n8n-nodes-base.github - If
n8n-nodes-base.if - Schedule Trigger
n8n-nodes-base.scheduleTrigger
What it does
Purpose This workflow creates a versioned backup of an entire Clockify workspace split up into monthly reports. How it works - This backup routine runs daily by default - The Clockify reports API endpoint is used to get all data from the workspace based on time entries - A report file is being retrieved for every month starting with the current one, going back 3 month in total by default - If changes happened during a day to any report, it is being updated in Github Prerequisites - Create a private Github repository - Create credentials for both Clockify and Github (make sure to give permissions for read and write operations) Setup - Clone the workflow and select the belonging credentials - Follow the instructions given in the yellow sticky notes - Activate the workflow