Skip to content
TWINJAM

Time tracking integration

Clockify entries that roll up into a real margin forecast.

Syncs Clockify time entries for client projects and splits them into contracted, uncontracted and recovered hours for margin telemetry.

Start free trialExplore the sandbox
Last reviewed Oct 5, 2026
Clockify logo
Vendor
CAKE.com
Plan
Agency and Scale plans
Authentication
Clockify API key (X-Api-Key header) and Clockify webhooks
Setup time
About 3 minutes
Sync
Real time via Clockify webhooks, with nightly reconciliation

Overview

How TWINJAM works with Clockify

Clockify is common in agencies with large or distributed delivery teams, where a free seat per person matters. TWINJAM reads entries for the projects you map and attributes each one to a contracted deliverable or an open scope flag, using project, task, tags and description.

Those attributions feed margin telemetry: contracted hours remaining, uncontracted hours already spent, and the forecast margin at completion if nothing changes. When a change order is approved, the recovered hours move out of the uncontracted bucket and the forecast updates on the same dashboard the founder and finance lead already watch.

TWINJAM authenticates with a workspace API key, subscribes to Clockify webhooks for new and updated entries, and ignores everything outside mapped projects.

In practice

Six points of margin, recovered

Sundial's Phase 2 shows 38.5 uncontracted hours in Clockify. After a signed change order recovers 24 of them, the margin forecast moves from 41% back to 47%, and the dashboard shows exactly which request made the difference.

The payload on the right is the event TWINJAM emits to your triage feed and to outbound webhooks, so you can route it into your own reporting.

Example event, Clockifyapplication/json
{
  "type": "margin.forecast.updated",
  "id": "mgn_K7c2Rd4F",
  "workspace": "SDL-SAAS",
  "source": {
    "tool": "clockify",
    "project": "Sundial Phase 2"
  },
  "hours": {
    "contracted": 410,
    "uncontracted": 38.5,
    "recovered_by_change_orders": 24
  },
  "forecast": {
    "contracted_fee_usd": 96000,
    "margin_at_completion": 0.47,
    "margin_if_unrecovered": 0.41
  }
}

Permissions

Scopes requested, and why.

ScopeWhy TWINJAM needs it
Workspace API key (admin)Clockify uses API key authentication. TWINJAM reads only mapped projects.

Events

What triggers a check.

  • NEW_TIME_ENTRY

    Attributes each new entry to a deliverable or flag.

  • TIME_ENTRY_UPDATED

    Re-attributes entries when descriptions, tasks or tags change.

  • TIME_ENTRY_DELETED

    Keeps uncontracted hour totals accurate.

Setup

Connect Clockify in about 3 minutes.

An admin connects once. PMs never need to re-authenticate, and you can revoke access from TWINJAM or the vendor's admin console at any time.

  1. 1Create an API key from a Clockify workspace admin profile.
  2. 2Add it in TWINJAM under Integrations, then Clockify.
  3. 3Map projects to contract workspaces and tasks to deliverables.
  4. 4TWINJAM registers webhooks and backfills 90 days of entries.

FAQ

Clockify integration questions

Time entries for mapped projects: duration, description, task, tags, billable flag. Project, client and task names. It never reads: projects outside the mapping; screenshots, GPS or kiosk data from Clockify add-ons; expense and invoice records.

Nothing. TWINJAM never edits or deletes entries. Every action that could reach a client requires a PM to approve it first.

Agency and Scale plans: Agency ($899/mo billed annually), Scale (from $1,800/mo billed annually). Every plan starts with a 14-day free production trial.

Real time via Clockify webhooks, with nightly reconciliation. Setup takes about 3 minutes.

Related integrations

All integrations

Put Clockify on the same page as your SOW.

Connect it during a 14-day free production trial and see the first flags from your live projects within days.

Start free trialRun a free SOW audit