Human Resources · Integration
Sapling
Add Sapling to your product for your customers, and give your AI agents governed access to it.
Sapling, now sold as part of Kallidus after the acquisition and rename, is an HR platform built around the joiner and leaver rather than around payroll. Its object model reflects that: an employee profile with the custom fields a company chose to collect, and workflows made of tasks assigned to people and due relative to a start or end date. An embedded Sapling integration is therefore most useful at the two moments that generate the most manual work, because a new hire or a departure can trigger the provisioning and removal your product owns in the customer's other connected systems. HR data is sensitive, so access is scoped per tenant, limited to the fields you map, and every read and write is logged. fastn holds the per-customer credentials and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Sapling account so employee profiles are readable inside your product without a file transfer.
React to a new hire or a departure so the access and setup your product owns happens on the right day rather than late.
Read onboarding and offboarding task state so your product can show what is outstanding before somebody's first day.
Map the custom profile fields, teams and locations a company configured, since no two organisations collect the same detail.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent lists which onboarding tasks are overdue for people starting this week, reading only that customer's account.
An agent updates a profile field it is permitted to change, with the write logged per tenant.
An agent reports which departures still have offboarding steps open, so nothing is left provisioned.
Example prompt
Who starts in the next two weeks, and which of their onboarding tasks has nobody completed yet?
Set up Sapling in 4 steps
- 01Enable the Sapling connector in your fastn dashboard.
- 02Have each customer authorise their own Sapling or Kallidus account with credentials scoped to the fields you need.
- 03Map the profile, team, location and custom fields your product uses, then enable the onboarding and offboarding triggers.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Sapling integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Sapling integration without building it. Your customers connect their own Sapling 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 Sapling update is not your on-call problem.
- One integration serves your product and your agents. The same governed Sapling 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
BambooHR
HiBob
PersonioOften used alongside
Tools the same teams tend to run next to Sapling, across other categories.
Slack
NetSuite
Notion
BoxSapling integration FAQ
How do I add a Sapling integration to my product?
Enable the Sapling connector in your fastn dashboard, then let each customer authenticate their own Sapling account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Sapling client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Sapling account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Sapling 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 Sapling 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 lists which onboarding tasks are overdue for people starting this week, reading only that customer's account.
Who maintains the Sapling integration?
fastn does. When Sapling 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 Sapling 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 Sapling 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 Sapling 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 Sapling integration?
A common starting point: let each customer connect their own Sapling account so employee profiles are readable inside your product without a file transfer. 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 Sapling integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Sapling does not change your per-connector cost. You can start free with 3 connected accounts.
Add Sapling to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.