Connect your app to BambooHR
Connect your Lovable app to BambooHR to display employee lists, show who is out of office, and update staff records. It uses a single shared connection that works both while prompting in chat and inside your published app.
Anyone building company directories, out-of-office boards, or internal HR dashboards using existing BambooHR data.
Do this, in order
- 1
Sign in to BambooHR, click your name in the lower left corner, select API Keys, create a new key, and copy it immediately.
BambooHR only displays the key once, and Lovable requires it to communicate with your HR account.
- 2
Identify your company subdomain from your BambooHR URL (for example, use 'acme' if your address is 'https://acme.bamboohr.com').
Lovable requires only the identifier prefix, not the entire web address.
- 3
In Lovable, navigate to Connectors, select BambooHR, click Add connection, and choose App + chat connector.
This creates a shared connector that functions both in the project builder chat and in live apps.
- 4
Enter your company subdomain and paste the API key under Configure connection.
Lovable needs these details to target and authenticate with your specific BambooHR account.
- 5
Under Sharing, decide whether to keep the connection private or share it with workspace members, then click Connect.
Lovable verifies the API key against BambooHR before saving the connection.
- 6
In your Lovable project chat, ask Lovable to link your project to BambooHR and build your desired HR tool.
Linking allows the project to read records, query time off, or update employee data.
Paste this into your project
Use BambooHR and build an employee directory with search by name, job title, and department. Include an out-of-office indicator showing who is taking time off this week.
Words decoded
- Subdomain
- The unique company name at the beginning of your web address, right before '.bamboohr.com'.
- API key
- A secure digital code that lets one app talk directly to another on your behalf without using your password.
- Cache
- Storing a temporary copy of data inside your app so it does not overload BambooHR with repeated requests.
Where people get stuck
- Entering your full web address instead of just the subdomain name when configuring the connection.
- Creating the API key with a user account that lacks the necessary permissions, which restricts what data the app can see.
- Failing to copy the API key right away, which requires generating a completely new one because BambooHR shows it only once.
- Assuming app visitors log in with their own BambooHR accounts; the connector uses a single shared key for everyone.
- Making too many live requests and hitting BambooHR rate limits instead of caching the data.
The short version, steps, decoder and prompt on this page are written automatically from Lovable's own documentation and can lag or misread it. The official page is always the authority.