OpenRuna
Sign in
← Workflows

Clockify Backup Template

21 nodes · extractFromFile, compareDatasets, stopAndError, splitOut, filter, clockify

Engine
n8n
Nodes
21
Trigger
scheduled/triggered
Source file
1896_Stopanderror_Splitout_Export_Scheduled.json

Workflow flow

IntegrationsExtractFromFileCompareDatasetsStopAndErrorSplit OutFilterClockifyHTTPGitHubScheduleSetIF
100%
TRIGGER

Schedule Trigger

Schedule

Get first workspace

Clockify

Globals

Set

Set month indexes

Set

Split Out indexes

Split Out

Set intervals

Set

Get detailed monthly report

HTTP

Check if file exists in GitHub

GitHub

Extract from File

ExtractFromFile

Point to new data

Set

Check for 404 error message

IF

Compare Datasets

CompareDatasets

Stop and Error

StopAndError

Skip empty reports

Filter

Update file in GitHub

GitHub

Create file in GitHub

GitHub

16 steps · flows top to bottom, branches left to right

Browse by integration

Browse all integrations →

Import into n8n

  1. Download the n8n JSON file (full or sanitized).
  2. In n8n: Workflows → Import from file.
  3. Open each node and reconnect credentials to your accounts.
  4. Test with manual execution before enabling triggers.

Sanitized JSON removes credential IDs — safer for sharing. Flow graph JSON is OpenRuna's lightweight format for diagrams and other tools, not n8n import.

View source corpus ↗

Overview

Clockify Backup Template is a free n8n workflow on OpenRuna — 21 nodes connecting extractFromFile, compareDatasets, stopAndError, splitOut, filter, clockify, httpRequest, github. Download the JSON, view the flow diagram, and import it into your n8n instance.

What this workflow does

This n8n workflow, "Clockify Backup Template", wires together extractFromFile, compareDatasets, stopAndError, splitOut, filter, clockify, httpRequest, github in 21 nodes. 21 nodes · extractFromFile, compareDatasets, stopAndError, splitOut, filter, clockify Execution begins at the scheduled/triggered trigger and flows through the 21 configured nodes. OpenRuna renders the node graph and offers the JSON export so you can import and adapt it in minutes. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

  • Import "Clockify Backup Template" into n8n, reconnect credentials for extractFromFile, compareDatasets, stopAndError, splitOut, filter, clockify, httpRequest, github, and run the same automation in your own workspace.
  • Use it as a starting template when wiring extractFromFile, compareDatasets, stopAndError, splitOut, filter, clockify, httpRequest, github — adjust node parameters to your accounts and record IDs.
  • Study how data moves from extractFromFile to compareDatasets before building your own variant.
  • Share it with your team as a documented reference for scheduled/triggered automations in the extractFromFile stack.

Example output

Imported into n8n, "Clockify Backup Template" exposes 21 configured nodes. Trigger type: scheduled/triggered. Integrations: extractFromFile, compareDatasets, stopAndError, splitOut, filter, clockify, httpRequest, github. Open each node after import to map credentials to your own extractFromFile and compareDatasets accounts. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Ask Claude to turn the "Clockify Backup Template" JSON into a plain-English runbook, node by node. It can flag where extractFromFile rate limits or missing retries might bite before you go live.

ChatGPT

Drop the workflow JSON or this OpenRuna page URL into ChatGPT and ask for a step-by-step runbook: triggers, branches, and which fields to customise for extractFromFile, compareDatasets, stopAndError, splitOut, filter, clockify, httpRequest, github. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "Clockify Backup Template" — extract extractFromFile IDs and secrets into environment variables without changing the 21-node structure.

Frequently asked questions

How do I import "Clockify Backup Template" into n8n?
Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.
Which integrations does "Clockify Backup Template" use?
It uses: extractFromFile, compareDatasets, stopAndError, splitOut, filter, clockify, httpRequest, github. The flow diagram above shows how each service connects across the 21 nodes. Filter OpenRuna by integration to find related workflows and tools.
Can I import a sanitized export without credentials?
Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own extractFromFile and compareDatasets credentials in n8n after import.
What trigger type does "Clockify Backup Template" use?
Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.
Is "Clockify Backup Template" free to use?
OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for extractFromFile, compareDatasets, stopAndError, splitOut, filter, clockify, httpRequest, github.

Related resources