Human Resources · Integration
Lucca
Add Lucca to your product for your customers, and give your AI agents governed access to it.
Embed a Lucca integration so your customers' people data drives your product without a manual import, using their own Lucca account rather than a file somebody emails once a month. Lucca is subscribed to module by module, so which data a customer has differs between them, and that is handled as per-tenant mapping instead of a branch in your code. Access is scoped per tenant and limited to the fields you map, credentials are encrypted, and every read and write is logged, which is the minimum bar for HR data. fastn owns the auth and API upkeep, and the same governed connection gives your AI agents scoped, audited access.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers connect their own Lucca account so employee records and org structure drive your product without a manual import.
Read absences and timesheets per tenant so your product plans around who is actually available.
Create or read expense claims so a spend your product knows about ends up where the finance team already works.
Support each customer's own Lucca modules and field setup as configuration, since the suite is bought module by module.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent answers a question about a team's leave from the customer's own data, reading only the fields you mapped.
An agent files or checks an expense claim within scoped permissions, with the write audited.
An agent flags timesheets that are still missing before a payroll cutoff.
Example prompt
Who on this team is on leave next week according to Lucca, and are any timesheets missing?
Set up Lucca in 4 steps
- 01Enable the Lucca connector in your fastn dashboard.
- 02Have each customer authorise their own Lucca account so calls run under their credentials.
- 03Map only the employee, absence, timesheet and expense fields your product actually needs.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Lucca integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Lucca integration without building it. Your customers connect their own Lucca 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 Lucca update is not your on-call problem.
- One integration serves your product and your agents. The same governed Lucca 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
HiBob
BambooHR
GustoOften used alongside
Tools the same teams tend to run next to Lucca, across other categories.
Slack
NetSuite
Notion
BoxLucca integration FAQ
How do I add a Lucca integration to my product?
Enable the Lucca connector in your fastn dashboard, then let each customer authenticate their own Lucca account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Lucca client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Lucca account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Lucca 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 Lucca 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 a question about a team's leave from the customer's own data, reading only the fields you mapped.
Who maintains the Lucca integration?
fastn does. When Lucca 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 Lucca 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 Lucca 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 Lucca 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 Lucca integration?
A common starting point: connect their own Lucca account so employee records and org structure drive your product without a manual 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 Lucca integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Lucca does not change your per-connector cost. You can start free with 3 connected accounts.
Add Lucca to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.