Automations that start before anyone asks
When Rippling reports a new hire, Risotto activates their Okta account, adds their groups and opens the laptop ticket. Write the steps in plain English, read tool inputs straight from the event, and choose which steps wait for approval.
Fill tool inputs straight from the event
An automation uses the same editor as a runbook: plain-English steps, tools added with #, and the same choice for every input of every tool.
- Set by author, from the event. Point the Okta group tool’s
user_emailatemployee_emailfrom Rippling. Every run uses the new hire’s exact address. - Set by author, a fixed value. Type the values that never change once, such as the All Employees group or the #new-hires channel.
- Set by agent. The agent fills in the rest from the event and your instructions, such as the ticket title.
Risotto adds the values from the event and the values you set when the tool runs. The agent can’t change them.
Joiner, mover and leaver, handled
Risotto acts when your HR system or Okta reports a change, not only when someone asks.
- Joiner. Rippling reports a new employee. Risotto activates the Okta account, adds groups, invites them to team Slack channels and opens a laptop ticket for IT.
- Mover. BambooHR reports an employment status change, such as a contractor who becomes full time. Risotto updates their groups to match.
- Leaver. HiBob reports that an employee left. Risotto suspends the Google Workspace account, signs them out everywhere and transfers their files to their manager, with IT approval on the steps you choose.
Every run is on record, with the event that started it. Open a run to see each step, and run it again when you need to. Before you turn an automation on, run it by hand with an event you edit, such as a sample new hire.
“Risotto’s AI-powered support is fully embedded in the way we operate, from day-one employee onboarding to providing technical support for seasoned team members.”
Start from any event
Okta A user is created, activated, suspended, deactivated, or locked out Learn more
Rippling An employee is created, hired, or terminated Learn more
BambooHR An employee is created, their employment status changes, or they are terminated Learn more
HiBob An employee is created, joins, or leaves Learn more
Tickets A ticket is created, escalated, or resolved
- A schedule Daily, weekly, monthly, or on your own schedule
- A webhook Any system sends an authenticated webhook to the automation’s own URL
Slack Connect Someone requests a Slack Connect invite
You choose when it stops and asks
Each automation has its own approval setting:
- Always. Every create, update and delete waits for an admin.
- Destructive changes. Creates and updates run, unless a tool requires approval. Deletes and revokes wait.
Start with Always. Change it when the runs look right. Admins set the highest level anyone in the organization can choose.
No code needed; code when you want it
Most automations are plain English. When a step must run exactly the same way every time, it runs as a script tool: TypeScript the Assistant writes and you can read.
- Script Studio shows each script tool as a flow chart, with test runs, run traces and templates.
- Nothing hidden behind a prompt. You review the code.
- Writes stay gated. Any script tool that changes data in your connected tools requires approval.
If it has an API, Risotto can automate it
- Native integrations for identity, devices, HR, ticketing and knowledge. All integrations
- Custom API tools. Give Risotto a vendor’s API spec or docs and it drafts the tools for your review. Templates cover common vendors.
- MCP servers. Connect any tool with an MCP server.
- Credentials stay locked. Secrets are write-only and go only to hosts you approve. Security and trust
Risotto’s own MCP server lets your team read and change automations, runbooks and tools from Claude or any MCP client, with OAuth sign-in and role-based permissions.
Frequently asked questions
How do I automate onboarding and offboarding from Rippling, BambooHR or HiBob?
Connect your HR system to Risotto and create an automation that starts on its new employee or termination event. Describe the steps, such as activating the Okta account and adding groups, set tool inputs from the event, and choose which steps need IT approval.
Can I trigger an IT automation from an Okta event or a webhook?
Yes. Risotto automations start when Okta reports that a user is created, activated, suspended, deactivated or locked out, and when any system sends an authenticated webhook to the automation’s own URL.
Can I build IT automations with AI and still review the code?
Yes. The Assistant shows every change as a draft before it saves. Script tool steps are TypeScript you can read in Script Studio, with test runs and traces.
Does an automation make changes without approval?
Only if you allow it. Each automation has its own approval setting: Always, where every create, update and delete waits for an admin, or Destructive changes, where only deletes and revokes wait. Admins set the highest level anyone in the organization can choose.
What is the difference between an automation and a runbook?
An automation starts on its own, from an event, a schedule or a webhook. A runbook tells Risotto how to handle a request an employee makes in Slack or Microsoft Teams. Both use the same editor and the same “Set by author” inputs.