Human Resources · Integration
Rippling
Add Rippling to your product for your customers, and give your AI agents governed access to it.
Rippling's premise is that the employee record drives everything else, including device and app provisioning, so the employee object is unusually central and unusually rich. That is useful for an integration because one read answers questions that elsewhere require three systems. Tokens inherit the permissions of whoever created them, which is a real design consideration rather than a footnote: a token made by an admin sees far more than one made by a manager, and your product should not assume the wider case. Departments and groups are how customers express their own structure, so mapping them is configuration. fastn keeps each customer's token scoped and its permissions visible.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Rippling account so the employee record drives your product too.
Read employees with their department and manager, which is the structure most features need.
Read time entries per person to show effort next to the work your product tracks.
React when someone joins or leaves, rather than discovering it on the next sync.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent answers reporting-line questions from the employee record rather than a stale export.
An agent reports who joined or left in a period, with each read audited per tenant.
An agent reacts to a departure and lists what your product needs to revoke.
Example prompt
Who reports into this department, and who joined or left in the last month?
Set up Rippling in 4 steps
- 01Enable the Rippling connector from your fastn dashboard.
- 02Have each customer authorise their own Rippling 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 Rippling integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Rippling integration without building it. Your customers connect their own Rippling 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 Rippling update is not your on-call problem.
- One integration serves your product and your agents. The same governed Rippling 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
Deel
Gusto
WorkdayOften used alongside
Tools the same teams tend to run next to Rippling, across other categories.
Slack
NetSuite
Notion
BoxRippling integration FAQ
How do I add a Rippling integration to my product?
Enable the Rippling connector in your fastn dashboard, then let each customer authenticate their own Rippling account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Rippling client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Rippling account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Rippling 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 Rippling 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 answers reporting-line questions from the employee record rather than a stale export.
Who maintains the Rippling integration?
fastn does. When Rippling 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 Rippling 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 Rippling 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 Rippling 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 Rippling integration?
A common starting point: let a customer connect their own Rippling account so the employee record drives your product too. 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 Rippling integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Rippling does not change your per-connector cost. You can start free with 3 connected accounts.
Add Rippling to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.