Human Resources · Integration
Employment Hero
Add Employment Hero to your product for your customers, and give your AI agents governed access to it.
Embed an Employment Hero integration so your customers can work their own employee records, onboarding, leave requests, and timesheets from inside your product. HR data is sensitive, so access is scoped per tenant and limited to the fields you map, credentials are encrypted, and every read and write is logged rather than exposing the whole employee record. fastn handles per-customer authorisation and API upkeep, so adding another organisation is configuration rather than a release.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers sync employee records and org structure from their own Employment Hero account into your product.
Read leave requests and timesheets so your product schedules and reports against real availability.
Create or update employee details from your product so HR admins do not re-key the same change twice.
Trigger your product when a new hire is onboarded or an employee is terminated, so downstream access follows.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent answers a question about leave balances or team structure using live records within scoped permissions.
An agent submits or updates a request on an employee's behalf, with every action attributed and audited.
An agent reacts to a new hire event and runs the onboarding checklist across the customer's other systems.
Example prompt
Show approved leave for this team over the next four weeks and flag any week where more than two people are away.
Set up Employment Hero in 4 steps
- 01Open the Employment Hero connector from your fastn dashboard.
- 02Have each customer authenticate their own Employment Hero account.
- 03Map the employee fields, leave types, and timesheet data your product uses, then enable actions and triggers.
- 04Call them from your product, or expose them to an agent through the MCP server.
Why teams use the Employment Hero integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Employment Hero integration without building it. Your customers connect their own Employment Hero 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 an Employment Hero update is not your on-call problem.
- One integration serves your product and your agents. The same governed Employment Hero 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
Deputy
ADP Workforce NowOften used alongside
Tools the same teams tend to run next to Employment Hero, across other categories.
Slack
NetSuite
Notion
BoxEmployment Hero integration FAQ
How do I add an Employment Hero integration to my product?
Enable the Employment Hero connector in your fastn dashboard, then let each customer authenticate their own Employment Hero account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Employment Hero client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Employment Hero account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Employment Hero 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 Employment Hero 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 leave balances or team structure using live records within scoped permissions.
Who maintains the Employment Hero integration?
fastn does. When Employment Hero 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 Employment Hero 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 Employment Hero 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 Employment Hero 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 Employment Hero integration?
A common starting point: sync employee records and org structure from their own Employment Hero account into your product. 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 Employment Hero integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Employment Hero does not change your per-connector cost. You can start free with 3 connected accounts.
Add Employment Hero to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.