Example: onboard a new hire (video)
A video of one onboarding from start to finish: a new hire added in Rippling starts an automation that sets up their accounts, waits for an admin to approve the access steps, and tells IT in Slack.
Watch one onboarding from start to finish. Your HR team adds a new hire in Rippling, and the New hire onboarding automation does the rest, with an admin approving the steps that change access. This example has no setup steps: to build the automation, see Automations, and to connect Rippling, see Rippling.
The automation is the New hire onboarding example from the library. It starts on Rippling's Employee created trigger and asks for approval on Destructive changes.
What happens
HR adds the new hire in Rippling
Northwind's HR team adds Maya Okafor in Rippling, with her work email, her department (Engineering) and her start date. Rippling sends events only for employees with access to Risotto in Rippling. See Automation triggers.
The automation starts
About five minutes later, Rippling sends Risotto an
employee.createdevent. That starts the New hire onboarding automation. Its instructions are six plain-language steps, each with a tool. See Rippling triggers.The run looks her up and creates her Google Workspace account
First, the agent looks Maya up in Rippling to find her department. Then it creates her Google Workspace account, in Engineering's organizational unit. Neither step waits: the first only reads, and the second is not a destructive change.
Three access steps wait for approval
The next three steps change access: activate her Okta account, add her to the Engineering group in Okta, and add her to the
#generaland#engchannels in Slack. At Destructive changes, these tools wait for an admin, so the run shows Awaiting approval. Dana, an IT admin, opens the run, checks each call in the Tool approval card, clicks Approve all, then Submit decisions. See Approving a paused run.The run picks up where it stopped
In Slack, Maya is now in
#generaland#eng, and her team sees her join. Then Risotto posts in#it-onboarding: who she is, her department, and her start date.Read the run's record
In the dashboard, the automation's Run history lists the run as an Event run, marked Success. Open it to see the event Rippling sent, the agent's summary under Result, and the Transcript, with who approved each change, and when. See Run history.
Related
- Automations: triggers, approvals, runs and run history
- Rippling: connect Rippling and use its automation triggers
Something wrong or missing? Report an issue · View as Markdown