Skip to content
NEWError doctor and Watchtower: failed n8n runs explained in plain words, and emailed to you. See what is new

Library / Code, Git & Developer Tools

Code, Git & Developer Tools

Back Up Clockify Reports to GitHub

On a schedule, it fetches Clockify time reports by month, compares them with stored files and commits new or changed data to GitHub.

What it does

# Clockify Backup Template ## Overview Automated workflow: Clockify Backup Template. This workflow integrates 12 different services: filter, httpRequest, stickyNote, scheduleTrigger, splitOut. It contains 23 nodes and follows best practices for error handling and security. ## Workflow Details - Total Nodes: 23 - Node Types: 12 - Error Handling: ✅ Implemented - Security: ✅ Hardened (no sensitive data) - Documentation: ✅ Complete ## Node Breakdown - Extract from File: extractFromFile - Compare Datasets: compareDatasets - Stop and Error: stopAndError - Globals: set - Set month indexes: set - Split Out indexes: splitOut - Set intervals: set - Skip empty reports: filter - Get first workspace: clockify - Get detailed monthly report: httpRequest - ... and 13 more nodes ## Usage Instructions 1. Configure Credentials: Set up all required API keys and credentials 2. Update Variables: Replace any placeholder values with actual data 3. Test Workflow: Run in test mode to verify functionality 4. Deploy: Activate the workflow for production use ## Security Notes - All sensitive data has been removed or replaced with placeholders - Error handling is implemented for reliability - Follow security best practices when configuring credentials ## Troubleshooting - Check error logs if workflow fails - Verify all credentials are properly configured - Ensure all required services are accessible

The steps

  1. Extract from File
  2. Compare Datasets
  3. Stop and Error
  4. Globals
  5. Set month indexes
  6. Split Out indexes
  7. Set intervals
  8. Skip empty reports
  9. Get first workspace
  10. Get detailed monthly report
  11. Check if file exists in GitHub
  12. Point to new data
  13. Check for 404 error message
  14. Update file in GitHub

26 steps in total.

Similar automations