Suptask’s Slack BambooHR integration lets AI answer time-off questions, add employee details to HR and IT tickets. With write access set to Off, Ask an agent for approval, or Auto per tool.



























Create a custom access level for BambooHR for Suptask. View-only access is meant for lookups, and edit access allows the assistant to make changes in fields. So choose the access level accordingly.
Add a BambooHR user for Suptask, one that is not a real employee, and set it to that access level.
Generate an API key for the BambooHR user and paste it into Suptask with your company domain before .bamboohr.com.
BambooHR connector is available with AI workflows on the Custom plan. Tickets from BambooHR events are posted in Slack available from a professional plan.
The setup is done in two places. In BambooHR, you should create a custom access level first, and then a dedicated user that is put on that level. The API key is generated for that user. In Suptask, the BambooHR connector is added to an Inbox, along with your company domain, which is the part before .bamboohr.com. Then you choose the tools the Assistant is allowed to use.
The app from BambooHR is made for the employees. It is used to check a time-off balance, to request time off, to see who’s out, and to look up a colleague. Suptask’s BambooHR Slack integration is for the help desk side of it. The tickets in your Slack help desk are carrying the employee’s details with them, and the Assistant is able to handle onboarding and the record changes, with an agent approving it.
Employee lookup, who’s out, the time-off balances, and the requests, these are the things it can read. For changes, you need Edit access at the access level, plus the tool turned on. Then an employee record can be created or updated by it. A time-off request can also be submitted or handled on behalf of the requester.
Yes, it can. BambooHR posts the event into a Slack channel for a new hire or someone’s last day, and Suptask makes a ticket out of that message. The message itself becomes the description on the ticket. For this one, the connector is not needed at all.
There are two levels of control on it. The access level in BambooHR decides what Suptask can ever reach, and this is the outer boundary. Inside that, every tool is set to Off, or to Ask, or to Auto, on each Assistant separately. Most teams should keep the lookups on Auto. The creation and updating of employees should be kept on Ask, so an agent approves it before it reaches BambooHR.
The connector is a part of the AI workflows, and that comes with the Custom plan. Additional cost might apply to it. The other direction is different. Tickets which are created from the BambooHR events posted in Slack are using automatic ticket creation, and that one is available from the Professional plan. The pricing page carries the full feature list for each plan.