Integrations and imports

Integrations bring activity into the work record or carry reviewed data to another system. Imports establish the starting point when a team already tracks time elsewhere. Treat both as data-boundary work with a named owner and a validation plan.

Choose the right connection

Open Settings and review the integration options available to your workspace:

• MCP setup: Connect supported AI clients through the hosted OAuth flow.
• Browser extensions: Capture supported browser-side time or attribution activity.
• API keys and personal access tokens: Authenticate deterministic integrations.
• OAuth applications: Let another application request workspace access from users.
• Webhooks: Send signed change events to your systems.
• Accounting: Connect supported finance workflows.
• Import: Connect Clockify and migrate supported records from that workspace. The platform does not currently provide a general CSV or file-upload importer.

For implementation details, open Developer docs.

Plan an import

Before importing from Clockify, define:

• The source Clockify workspace and cutover date.
• The records and plan-limited history in scope.
• How users, clients, projects, workstreams, tags, and billable state map.
• Which system remains authoritative after cutover.
• How duplicates will be detected.
• Who approves the result.

Use the preview to inspect counts before starting the import. After it completes, review a representative client project, internal project, billable and non-billable time, several members, and important tags or workstreams.

Validate the result

Compare source and destination totals by more than one dimension:

1. Total duration for the imported date range.
2. Duration by member.
3. Duration by client and project.
4. Billable and non-billable totals.
5. A sample of descriptions, timestamps, tags, and rates.

Totals can match while individual records are mapped incorrectly, so combine reconciliation with spot checks.

Cut over cleanly

Choose a cutover time and tell the team which system to use after it. Freeze or clearly mark the source period, run the final import, repeat reconciliation, and record any accepted differences.

Avoid keeping two active writers for the same time period. If a temporary overlap is unavoidable, define which records win and how duplicates will be removed.

Operate an integration

Assign an owner for credentials, delivery failures, and schema changes. Use least-privilege scopes, rotate secrets according to policy, verify webhook signatures, and monitor reporter or connection health.

An integration is complete when failures are visible and recoverable, not when the first successful record appears.

Import and Accounting settings require an owner or admin. Clockify import availability and history limits depend on the workspace entitlements; Accounting additionally requires invoicing to be enabled.