WorkTracker › Connection guides › TimeLog

Connect TimeLog to WorkTracker

The whole TimeLog site syncs with one set of Reporting API credentials.

What you need

• A TimeLog plan that includes “Integrations and APIs” (Growth or higher — the Starter plan excludes API access).
• A WorkTracker operator connects it under the company’s apps — TimeLog’s API has no per-user tokens that can read registrations, so this is a company-level connection by design.

Setup

1. Find your Reporting API credentials

   In TimeLog open System Administration → Integrations and API → Reporting API settings. Note the three values: site code, API ID and API password — and your TimeLog URL (like https://app3.timelog.com/yourcompany) shown under the API settings.

2. Connect the company

   In WorkTracker (as operator) open Admin → Companies, expand the company’s apps and fill the TimeLog form with the URL and the three credentials. Tick “migrate full TimeLog history” to bring up to ten years of registrations.

3. Sync

   Press “sync now”. Registrations, projects and customers stream in; the row shows the outcome. After that it stays in sync automatically every 30 minutes.

What WorkTracker collects

• All employees’ time registrations (read) — each one attributed to the right person by email.
• Projects and customers (read) — they fill the company registry for budgets and reports.
• The employee list (read) — teammates without a WorkTracker account become pending accounts, claimable by invite.

The credentials are stored encrypted (AES-256-GCM). WorkTracker only reads from TimeLog. Note that TimeLog registers time as hours per day — start and end clock times appear only if your TimeLog site has the optional Timestamps feature enabled; other registrations land on their date with a duration. Credentials are stored encrypted (AES-256-GCM) and are never shown again or returned by the API.

Troubleshooting

Some employees did not get their time

Employees are matched by email. TimeLog members without an email address on their employee record cannot be attributed — add the email in TimeLog and run a full re-sync.