Before
Managers or IT staff likely reviewed recent BambooHR changes, gathered each new hire’s details, and entered them separately into multiple access systems. They also had to announce the arrival and follow up with a completion message after the accounts and invitations were handled.
How it works
- Retrieve employee records changed since the previous day and identify the new-hire details needed for onboarding.
- Process each employee by announcing the arrival and creating or inviting accounts across the required workplace systems.
- Post a completion notification after the access setup sequence finishes for the employee.
Workflow details
- Trigger and employee lookup: The workflow can be run manually or scheduled daily, calculates the previous day’s date, and retrieves BambooHR employee records changed since that date, including identity, job, department, email, hire-date, and supervisor details.
- Per-employee onboarding: Each returned employee is processed individually, with the workflow creating an account in Okta, inviting the employee to Slack, and creating user accounts in Google Workspace and Office 365.
- Team communication: A new-hire arrival announcement is posted during the onboarding sequence so the relevant team can be informed as access setup begins.
- Completion handoff: After the employee’s access actions finish, the workflow posts an onboarding completion notification, providing a clear signal that the automated setup has reached its final stage.
- Operational control: The flow stops if a configured onboarding action fails, rather than silently proceeding as though the employee’s setup were complete.
What changed
New-hire access setup now starts from a daily or manual BambooHR review and runs through the required account creation, invitation, and notification steps automatically for each employee. The completion message is generated by the workflow, while a failed setup action stops the sequence instead of allowing an incomplete onboarding process to appear finished.
Work removed
Reviewing recent employee changes one by one, copying employee details between systems, creating Okta, Google Workspace, and Office 365 accounts, sending Slack invitations, posting new-hire announcements, and manually notifying stakeholders when onboarding is complete.
Expected outcome
For each employee, the workflow can remove at least four separate account or invitation actions and two notification handoffs, helping make workplace access available through a consistent onboarding sequence.
