Notion to Clockify Sync Template — AI Product | Success.
Notion to Clockify Sync Template Notion to Clockify Sync Template — free, ready-to-import n8n workflow (68 nodes, Databases Storage).
AI Product Reusable license
from $0
Understand this workflow before you use it.
Structure unavailable 1 to review Health 96/100 Workflow structure could not be fully reconstructed from the source file The source file lists the steps but not how they connect. Steps, integrations and security checks are analyzed; execution order and structure-based checks are not. This is a limitation of the file, not necessarily a problem with the workflow.
This workflow starts from Webhook and Schedule and works with documents and a schedule.
Steps 56
Integrations 1
Connections Unavailable
Complexity Advanced
Technical health 96/100
Security 1 to review Sale models Live demo Payments run through a deterministic mock provider in this environment — no real money moves.
**Notion to Clockify Sync Template**
Category: Databases Storage · 68 nodes
Nodes/integrations used: clockify, compareDatasets, httpRequest, limit, notion, scheduleTrigger, stopAndError, webhook
How to use: download the JSON below, then in n8n choose Import from File (or open the demo link, copy the JSON, and paste with Ctrl+V into the n8n canvas). Add your own credentials and activate.
Source: Zie619/n8n-workflows (MIT). Credentials were removed and files modified for redistribution — see the library's ATTRIBUTION_AND_LICENSES.md for full license text.
Workflow structure Steps and detected references (no diagram) Execution order can't be reliably reconstructed from this file, so no diagram is shown. Here is what the workflow contains.
40 × Logic 9 × App 3 × Flow control 2 × HTTP 1 × Schedule 1 × Webhook Webhook · Webhook Globals · Set Schedule Trigger · Schedule Get first workspace ID · Clockify Compare Datasets · Compare Datasets Stop and Error · Stop and Error Structure output · No-Op Map values · Set Map values1 · Set No Operation · No-Op Get active Clients from Notion · Notion Get active Clients from Clockify · Clockify If unmapped in Notion · If Set new values · Set Update Client in Clockify · Clockify Get archived Client from Notion · Notion Create Client in Clockify · Clockify Store Clockify ID in Notion · Notion Remove Client from Clockify · Clockify Merge · Merge No Operation, do nothing · No-Op Get active Projects from Notion · Notion Get active Projects from Clockify · Clockify Update Project in Clockify · HTTP Request Get completed Project from Notion · Notion Create Project in Clockify · HTTP Request Remove Project from Clockify · Clockify Structure output1 · No-Op No Operation1 · No-Op Map values2 · Set Map values3 · Set Compare Datasets1 · Compare Datasets If unmapped in Notion1 · If Set new values1 · Set Store Clockify ID in Notion1 · Notion Stop and Error1 · Stop and Error Merge1 · Merge No Operation, do nothing2 · No-Op Get active Tasks from Notion · Notion Get active Tasks from Clockify · Clockify + 16 more steps
Detected references These steps name another step whose data they read. That shows a data dependency, not the order the steps run in.
Get active Clients from Clockify reads data from Globals Update Client in Clockify reads data from Compare Datasets Update Client in Clockify reads data from Globals Create Client in Clockify reads data from Globals Store Clockify ID in Notion reads data from Get active Clients from Notion Remove Client from Clockify reads data from Create Client in Clockify Remove Client from Clockify reads data from Globals Get active Projects from Clockify reads data from Globals Update Project in Clockify reads data from Compare Datasets1 Create Project in Clockify reads data from Get active Projects from Notion Remove Project from Clockify reads data from Compare Datasets1 Remove Project from Clockify reads data from Globals Security 1 note(s) to review 0 Critical0 High1 Medium0 Low0 InfoMedium Webhook accepts unauthenticated requests
Anyone who learns the webhook URL can trigger this workflow with arbitrary data.
Confidence: medium · Heuristic
Suggested fix: Enable header or basic auth on the Webhook node, or verify a signature from the sending service.
Health How the technical score is made up Overall 96/100 .
Technical hygiene signals detected statically from the workflow file. Not a guarantee of correctness or fitness for a particular use.
Execution profile What one run touches Starts from: Webhook, Schedule
HTTP requests 2 Loops and branching can't be measured without the workflow's connections.
Documentation Generated from the workflow's structure What it does This workflow starts from Webhook and Schedule and works with documents and a schedule.
Services involved: Notion.
This description is generated from the workflow's node types and wiring. It does not interpret each node's configuration.
Inputs Data enters through the trigger(s) below.
Webhook Schedule Trigger (Schedule) Main flow This file does not contain its real connections, so the execution order cannot be documented.
It contains: 40 × logic, 9 × productivity, 3 × flow, 2 × http, 1 × schedule, 1 × webhook.
Some steps name another step whose data they read. This shows data dependencies only, not the order steps run in:
Get active Clients from Clockify (Clockify) reads data from Globals (Set) Update Client in Clockify (Clockify) reads data from Compare Datasets Update Client in Clockify (Clockify) reads data from Globals (Set) Create Client in Clockify (Clockify) reads data from Globals (Set) Store Clockify ID in Notion (Notion) reads data from Get active Clients from Notion (Notion) Remove Client from Clockify (Clockify) reads data from Create Client in Clockify (Clockify) Remove Client from Clockify (Clockify) reads data from Globals (Set) Get active Projects from Clockify (Clockify) reads data from Globals (Set) Update Project in Clockify (HTTP Request) reads data from Compare Datasets1 (Compare Datasets) Create Project in Clockify (HTTP Request) reads data from Get active Projects from Notion (Notion) Outputs Without connection data, final outputs can't be identified precisely. These nodes write to external services:
Get active Clients from Notion (Notion) Get archived Client from Notion (Notion) Store Clockify ID in Notion (Notion) Get active Projects from Notion (Notion) Get completed Project from Notion (Notion) Store Clockify ID in Notion1 (Notion) Get active Tasks from Notion (Notion) Get completed Task from Notion (Notion) Store Clockify ID in Notion2 (Notion) Requirements No credentials are attached in this file. You will need your own n8n credentials for each service below.
Setup Import the JSON file into n8n (Workflows → Import from File). Create credentials for each service and select them on the matching nodes. Set environment variable(s): BASE_URL, WEBHOOK_URL. Reconnect the nodes in the n8n editor: this file's original connections are missing. Run it once manually with test data before activating. Important considerations 22 node(s) retry or continue on failure.
There is no Error Trigger in this workflow.
Generated automatically from the workflow's structure. Verify behaviour in n8n before relying on it.
Optimization ideas Advisory suggestions Potential optimization · high confidence
No-op placeholder nodes
8 "No Operation" nodes do nothing at runtime.
Possible impact: Cleaner graph; no runtime change.
No-op nodes are sometimes kept deliberately as visual end markers.
Automated static analysis (engine 1.1.0). Nothing was executed. Not a guarantee of correctness or safety.
The seller has not attached downloadable files yet.
Uploaded by the seller and security-scanned before any buyer can download them.
Documentation
LeadBot 24h — WhatsApp AI Lead Qualification Bot — free, ready-to-import n8n workflow (6 nodes, WhatsApp).
AI Product Reusable
Store Clockify ID in Notion1
Get active Projects from Notion
Get active Tasks from Clockify reads data from Globals
Update Task in Clockify reads data from Compare Datasets2 Be the first to review this product.
