Human Resources · Integration
BeeBole
Add BeeBole to your product for your customers, and give your AI agents governed access to it.
BeeBole's API is a single POST endpoint, https://beebole-apps.com/api/v2, where the operation is named in a `service` field of the JSON body, such as time_entry.list, person.list, absence.list or company.list. Authentication is HTTP Basic with the API token as the username and a throwaway character as the password, which trips up clients that expect a bearer token. The URL is exact: posting to the same path with a trailing slash returns 404 rather than the 401 you get from the correct one, so a misconfigured base URL fails in a confusing way. Time entries are recorded against a hierarchy of company, project, task and person, and a listing call needs a date range plus the right scope, because an unscoped query will not return every person's time by default. Absences and time entries are separate services, so total working time for a period has to be assembled from both. fastn holds each customer's token, deals with the Basic-auth and single-endpoint conventions and keeps the connection maintained.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own BeeBole account so logged hours flow into your billing or project view
Post time entries from your own task interface so staff do not have to enter hours twice
Read absences alongside time entries to show a true picture of a team's working time
Sync your project and task list into BeeBole so hours are booked against the right codes
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent which people have not submitted time for last week within one tenant
Have an agent total billable hours by project for a date range and prepare the invoice lines
Let an agent log a correcting time entry, with the write audited per tenant against that tenant's own token
Example prompt
How many hours did the team book to the Redesign project last month, and who was on leave?
Set up BeeBole in 4 steps
- 01Enable the BeeBole connector from your fastn dashboard.
- 02Have each customer authorise their own BeeBole 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 BeeBole integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a BeeBole integration without building it. Your customers connect their own BeeBole 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 BeeBole update is not your on-call problem.
- One integration serves your product and your agents. The same governed BeeBole 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
Workday
BambooHR
GustoOften used alongside
Tools the same teams tend to run next to BeeBole, across other categories.
Slack
NetSuite
Notion
BoxBeeBole integration FAQ
How do I add a BeeBole integration to my product?
Enable the BeeBole connector in your fastn dashboard, then let each customer authenticate their own BeeBole account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no BeeBole client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own BeeBole account?
Yes. Every connection is scoped to the individual customer, so each authorises their own BeeBole 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 BeeBole integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Ask an agent which people have not submitted time for last week within one tenant
Who maintains the BeeBole integration?
fastn does. When BeeBole 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 BeeBole 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 BeeBole 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 BeeBole 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 BeeBole integration?
A common starting point: let a customer connect their own BeeBole account so logged hours flow into your billing or project view. 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 BeeBole integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding BeeBole does not change your per-connector cost. You can start free with 3 connected accounts.
Add BeeBole to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.