Human Resources · Integration
Connecteam
Add Connecteam to your product for your customers, and give your AI agents governed access to it.
Connecteam authenticates with an X-API-KEY header on api.connecteam.com, and each key is generated per integration and scoped to particular features such as users, time clock or job scheduling. Missing scope produces an authorisation error rather than an empty result set, which is the most common first-run surprise. Users are the anchor object and carry custom fields defined per company that are referenced by field id rather than by label, so a mapping step between your schema and theirs is unavoidable. Time-clock entries belong to a named clock and a single shift can hold several timestamps plus manual edits, so worked hours are derived from the entries rather than read from one total field. Scheduler jobs are a separate resource with their own ids and do not share keys with the time clock. fastn holds each customer's key, checks which scopes it actually carries and keeps the connector current.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Connecteam account so your app reads their staff list without a CSV import.
Pull time-clock entries for a pay period and compute hours from the raw timestamps and edits.
Create or update users, populating the company's own custom fields by field id.
Read scheduled jobs and shifts to show a deskless team's coverage inside your product.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Have an agent report who clocked in late on a named clock, with every Connecteam read audited per tenant.
Ask an agent to check whether a shift has an open clock-in with no matching clock-out.
Let an agent look up a user's custom field values before a manager approves a change.
Example prompt
Who clocked in late on the warehouse clock yesterday?
Set up Connecteam in 4 steps
- 01Enable the Connecteam connector from your fastn dashboard.
- 02Have each customer authorise their own Connecteam 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 Connecteam integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Connecteam integration without building it. Your customers connect their own Connecteam 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 Connecteam update is not your on-call problem.
- One integration serves your product and your agents. The same governed Connecteam 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
Often used alongside
Tools the same teams tend to run next to Connecteam, across other categories.
Connecteam integration FAQ
How do I add a Connecteam integration to my product?
Enable the Connecteam connector in your fastn dashboard, then let each customer authenticate their own Connecteam account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Connecteam client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Connecteam account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Connecteam 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 Connecteam integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Have an agent report who clocked in late on a named clock, with every Connecteam read audited per tenant.
Who maintains the Connecteam integration?
fastn does. When Connecteam 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 Connecteam 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 Connecteam 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 Connecteam 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 Connecteam integration?
A common starting point: let a customer connect their own Connecteam account so your app reads their staff list without a CSV import. 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 Connecteam integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Connecteam does not change your per-connector cost. You can start free with 3 connected accounts.
Add Connecteam to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.