Human Resources · Integration
clockodo
Add clockodo to your product for your customers, and give your AI agents governed access to it.
clockodo requires an X-Clockodo-External-Application header on every single request, formatted as an application name and a contact email address, and calls without it are rejected no matter how good the credentials are; authentication itself is X-ClockodoApiUser plus X-ClockodoApiKey, or the same pair sent as HTTP Basic. The API at my.clockodo.com/api covers entries, entry texts, customers, projects, services, users, teams, absences, overtime and work times, and the distinction between an entry, which is time booked against a project and service, and a work time, which is attendance recorded for working time law, is the thing integrations most often conflate. Every entry must reference a service, so importing time without first mapping to the customer's own service list fails rather than falling back to a default. The v2 endpoints changed the response envelope and paginate differently from the legacy paths that have since been retired, so the version has to be explicit in the URL. fastn holds each customer's API user and key, sets the external application header for them and tracks the deprecations.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own clockodo account so time recorded in your product lands against the right project and service
Read absences and holidays so your scheduling view does not assign work to someone who is away
Pull work times and overtime balances into a payroll export without asking the customer to run a manual report
Create customers and projects in clockodo when they are set up in your system, so the service mapping stays consistent
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent to list unbilled entries for a customer's project this month, with the read audited per tenant
Have an agent flag users whose recorded work times and booked entries disagree by more than an hour a day
Let an agent summarise absence coverage for a team for the coming fortnight
Example prompt
How many hours have we booked against the Meridian project this month, and how much is unbilled?
Set up clockodo in 4 steps
- 01Enable the clockodo connector from your fastn dashboard.
- 02Have each customer authorise their own clockodo account, so calls run under their credentials rather than a shared key.
- 03Decide which employees, employment records and working time your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the clockodo integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a clockodo integration without building it. Your customers connect their own clockodo account inside your product and work their employees, employment records and working time there, with no per-customer code on your side.
- Handle the part that actually costs time: HR data is sensitive and its access rules are stricter than most systems. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a clockodo update is not your on-call problem.
- One integration serves your product and your agents. The same governed clockodo connection powers in-product features and gives AI agents scoped, audited access, so you keep people data current without manual re-entry without wiring it twice.
Used by these teams
Compare with
Workday
BambooHR
GustoOften used alongside
Tools the same teams tend to run next to clockodo, across other categories.
Slack
NetSuite
Notion
Boxclockodo integration FAQ
How do I add a clockodo integration to my product?
Enable the clockodo connector in your fastn dashboard, then let each customer authenticate their own clockodo account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no clockodo client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own clockodo account?
Yes. Every connection is scoped to the individual customer, so each authorises their own clockodo account and only ever sees their own employees, employment records and working time. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this clockodo integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Ask an agent to list unbilled entries for a customer's project this month, with the read audited per tenant
Who maintains the clockodo integration?
fastn does. When clockodo changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
How is sensitive clockodo employee data handled?
Access is scoped per tenant and limited to the fields you map, credentials are encrypted, and every read and write is logged. You expose only what your product actually needs rather than the whole employee record.
Can joiner, mover and leaver changes be automated?
Yes. Where clockodo is where a hire, a role change or a departure is recorded, that change can trigger downstream provisioning or removal across the customer's other connected systems. Where clockodo sits downstream of the HR system of record, the same event can be pushed into it so its worker list, schedules and access stay in step, which is where most of the manual effort sits.
What can I build with the clockodo integration?
A common starting point: let a customer connect their own clockodo account so time recorded in your product lands against the right project and service. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the clockodo integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding clockodo does not change your per-connector cost. You can start free with 3 connected accounts.
Add clockodo to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.