Human Resources · Integration
TCP Humanity
Add TCP Humanity to your product for your customers, and give your AI agents governed access to it.
Humanity, from TCP Software, schedules shift-based workforces: retail floors, clinics, kitchens, support desks. The objects are the shift and the schedule it belongs to, the positions and skills that decide who may work it, employee availability and time-off requests, and the clock-in records that say what actually happened. Location matters as much as it does in any rostering system, because coverage is a question about one site at one time rather than about the company. The care goes into the gap between the plan and reality: a published shift, a swap, a no-show and a clocked hour are four different facts, and a product that treats them as one will report coverage that never existed. Rostering feeds pay, so the connection stays scoped to one tenant, carries only the fields you mapped, and records every write.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Humanity account so schedules and coverage appear inside your product per location.
Create or amend a shift when demand changes, respecting the positions and skills that shift requires.
Read availability and time-off so your product never offers a shift to somebody who cannot take it.
Compare clock-in records against the published schedule, so your product reports hours worked rather than hours planned.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent finds tomorrow's uncovered shifts at a site and who is qualified and free to take them.
An agent publishes or reassigns a shift within scoped permissions, with the change attributed.
An agent explains where clocked hours diverged from the schedule last week and by how much.
Example prompt
Which shifts at this location are still unfilled this week, and who has the right position and is available?
Set up TCP Humanity in 4 steps
- 01Enable the TCP Humanity connector in your fastn dashboard.
- 02Have each customer authorise their own Humanity account so schedule reads and writes run under their credentials.
- 03Map the location, position, shift and clock-in fields your product uses, then enable the triggers you need.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the TCP Humanity integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a TCP Humanity integration without building it. Your customers connect their own TCP Humanity 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 TCP Humanity update is not your on-call problem.
- One integration serves your product and your agents. The same governed TCP Humanity 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
Deputy
BambooHR
GustoOften used alongside
Tools the same teams tend to run next to TCP Humanity, across other categories.
Slack
NetSuite
Notion
BoxTCP Humanity integration FAQ
How do I add a TCP Humanity integration to my product?
Enable the TCP Humanity connector in your fastn dashboard, then let each customer authenticate their own TCP Humanity account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no TCP Humanity client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own TCP Humanity account?
Yes. Every connection is scoped to the individual customer, so each authorises their own TCP Humanity 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 TCP Humanity integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent finds tomorrow's uncovered shifts at a site and who is qualified and free to take them.
Who maintains the TCP Humanity integration?
fastn does. When TCP Humanity 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 TCP Humanity 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 TCP Humanity 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 TCP Humanity 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 TCP Humanity integration?
A common starting point: let each customer connect their own Humanity account so schedules and coverage appear inside your product per location. 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 TCP Humanity integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding TCP Humanity does not change your per-connector cost. You can start free with 3 connected accounts.
Add TCP Humanity to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.