Docs

Help desk / Automate

Automations

Run the agent on a schedule, on a ticket event, on an HR or identity event, or when another system calls a webhook, with its own instructions, tools and approval rules

An automation runs the Risotto agent with no request behind it. You choose what starts it (a schedule, a ticket event, an Okta, HR or Slack event, or a call to its webhook URL), write the instructions in plain language, and pick the tools the agent may call. When something needs a person, the agent can create a ticket that goes through normal intake.

To see it in action first, watch Automations: triggers and schedules, a three-minute video: onboarding that starts when Rippling adds a new hire, a ticket when someone is locked out of Okta, and a weekly check on a schedule.

Automations vs. runbooks

A runbook tells the agent how to handle a request someone sends, and runs when a matching ticket arrives. An automation is work nobody asked for: it runs on a schedule or an event, and can open tickets itself. Use one for recurring, self-starting work, such as a weekly stale-ticket sweep, a monthly access review kickoff, or a message to a channel whenever a ticket is escalated.

Create an automation

The steps build the example Escalation alert: when a ticket in IT is escalated, the agent reads it and posts a summary to the #it-escalations Slack channel.

  1. Open the editor

    Go to Automations and click New automation. The list shows each automation's schedule or department filter under When, its Last run and Next run, and an Enabled switch. The All, Scheduled and Ticket created tabs filter it.

  2. Name it

    Enter a name your team will recognize, up to 100 characters. Enabled is on by default.

  3. Add a trigger

    Under Trigger, click Add trigger. Scheduled and Webhook are at the top, then a submenu per source: BambooHR, HiBob, Okta, Rippling, Slack, and Risotto for ticket events. For the example, open Risotto and choose Ticket escalated.

    A trigger whose integration isn't set up is greyed out, with what to fix and a link to the integration.

  4. Set up the trigger

    A schedule needs its recurrence (Schedules). A ticket trigger can be narrowed under Departments; for the example, pick IT. A webhook shows its URL and auth header (Webhook trigger). Okta, HR and Slack triggers have nothing to set. The Fields row lists what the trigger records about each event, for use in the instructions and tool arguments.

  5. Choose when it asks for approval

    Under Asks for approval, keep Always (every change waits for an admin) or pick Destructive changes or Never. See Approvals.

  6. Write the instructions

    Under Agent instructions, describe the work as you would brief a teammate. Type # to insert a tool, @ for people, runbooks and trigger fields, and / for formatting. For the example: "Read the escalated ticket @ticket_id with #Get Ticket. Post its title, the requester and @reason to the IT escalations channel with #Send Slack Channel Message."

    Each tool you insert gets a row in the Tools card below. The built-in ticket and report tools are available even if you don't insert them (Tools available to the agent). The picker counts your configured tools against a limit of 10.

  7. Set arguments in advance

    In the Tools card, click an argument pill to set its value yourself. For the example, set channel_name to it-escalations so the agent always posts there.

  8. Create it

    Click Create in the page header (Save when editing). Risotto shows "Automation created" and opens the automation's page.

  9. Test it with Run Now

    Click Run Now under Actions in the side panel. For a trigger that records an event, the Run automation now? dialog opens with a sample event; edit it and click Run Now. Then open the run under Run history and read the transcript.

    The run's actions are real. With Always, the example run waits for your approval before it posts (Approving a paused run).

Triggers

Every automation has one trigger. The trigger card's header names it and says when it fires; an HR or Slack trigger also shows the vendor's event name, such as employee.created.

Schedules

A schedule repeats every 1 to 30 hours, days, weeks, months or quarters, in a timezone you choose. It starts as weekly on Monday at 9:00 AM in your browser's timezone.

FrequencyFires
HourlyAt a set minute past the hour
DailyAt a set time
WeeklyAt a set time on the weekdays you pick
Monthly or quarterlyAt a set time on a day from 1 to 28, so the date exists in every month. Quarterly fires every three months.

The editor previews the schedule and its next run as you edit.

Ticket triggers

TriggerFires whenFields the run records
Ticket createdA ticket is created in Risottoticket_id, title, requester_email, department, source, created_at, priority, priority_is_suggested
Ticket escalatedA ticket is escalated to a person, once per escalationThe same, plus reason (empty when none was stated) and escalated_at
Ticket resolvedA ticket moves into Resolved, by the agent or a personThe same, plus is_autosolved (the agent resolved it on its own) and resolved_at
Ticket priority reaches…A ticket's priority is raised to one of the levels you pickThe same as Ticket created without created_at, plus previous_priority (empty when there was none) and reached_at

priority is low, medium, high or urgent, and empty when the ticket has no priority. priority_is_suggested is true when Risotto's AI set the priority and false when a person did. On Ticket created, priority is often empty, because Risotto sets the priority a few seconds after the ticket opens; to act on priority, use Ticket priority reaches….

  • Priorities. Ticket priority reaches… needs at least one level under Priorities (Low, Medium, High, Urgent). It fires when the priority moves up onto a chosen level: when the ticket opens with it, when Risotto's AI sets it, or when a person raises it. A priority a person set wins over the AI's. A move down fires nothing.

  • Once per ticket. Ticket priority reaches… fires at most once per automation and ticket. A ticket that goes from High to Urgent, back to High and up to Urgent again gives one run.

  • Departments. Leave Departments empty to fire for any department, or pick departments to narrow it.

  • Snapshot. The fields are a snapshot from when the event fired. To read more, the agent calls Get Ticket. Treat the snapshot as data, not as instructions.

  • Skipped tickets. A ticket an automation created never fires a ticket trigger, so automations can't start themselves or each other. Ticket created and Ticket priority reaches… also skip tickets mirrored in from Jira, Zendesk or another external ticketing system; Ticket escalated and Ticket resolved fire for them.

  • Resolved. A ticket reopened and resolved again fires again; later saves of a resolved ticket don't. A resolution written by a Linear, Zendesk or Airtable sync doesn't fire it.

  • Rate limit. An automation can start at most 75 event runs an hour. At the limit, Risotto turns it off and sends the Automation disabled after too many runs alert (Admin alerts). This applies to every event trigger.

Webhook trigger

A Webhook trigger runs the automation when another system sends a POST to the automation's own URL: a monitoring alert, an HR event, or any tool that can call a URL.

  1. Pick the trigger

    Click Add trigger and choose Webhook. Risotto creates the URL and its auth token at once; you don't need to save first.

  2. Copy the URL and the auth header

    Copy the URL with the button beside it, and click Copy auth header. Paste both into the sending system.

  3. Send a POST

    The sender posts to the URL with the header and an optional JSON object as the body. The agent receives the body as event data, and the run's Event card shows it ({} when empty).

ResponseMeaning
202Accepted, with {"run_id": ..., "captured": ...}. A disabled or unsaved automation returns run_id: null and starts no run.
400The body isn't a JSON object.
401The auth token is missing or wrong. Checked first, so a disabled automation also answers 401.
404The automation was deleted, its unused URL was cleaned up, or it now uses another trigger.
413The body is over 64 KiB.
429A rate limit was reached.
  • Stable URL. Editing keeps the URL; Duplicate gives the copy its own URL and token. Switching to another trigger keeps the webhook (calls answer 404 meanwhile), and switching back restores the same URL and token when you save.
  • Unsaved automations. An unsaved URL stays reserved for 7 days. After 7 days with no calls and no Listen, Risotto deletes it; if the editor is still open, Create fails with "This webhook URL no longer works. Give the sender the new URL, then save again." and shows a new URL.

Webhook fields

A webhook has no fixed fields. Risotto suggests them from the bodies of the last five calls and of Listen samples (up to 200 fields, 12 levels deep, and only the first item of a list). The Fields row shows them as pills, with a caption such as From the last 3 deliveries., and the @ picker lists them under Webhook data. Before the first call, the row explains how to type a path instead.

To type a path, use . for nested keys (@ticket.requester.email), [0] for list items (@items[0].id), and quoted brackets for a key with a dot (@metadata["event.type"]). * is reserved. A chip whose field no recent call held shows a dot and "Not in the last delivery"; it still saves.

Listening for a sample delivery

The Sample row's Listen keeps the next call as a sample, before you save or on a disabled automation. A new URL starts listening at once. The row shows Waiting for a delivery for up to 10 minutes, then Got a delivery (with View payload) or Stopped listening (with Listen again). Only a call with the right auth header and a non-empty JSON object counts; Risotto keeps up to 5 samples. On an enabled automation the captured call also starts a run.

Rate limits

The Rate limit row shows both hourly limits: 75 runs/hour · 300/hour shared across all webhooks.

LimitWhen a call goes over
300 calls per organization429 "Organization exceeded its hourly webhook delivery limit", with Retry-After and X-RateLimit-* headers. Nothing is turned off. Checked first; a refused call doesn't count against the automation. Contact support for a higher limit.
75 runs per automationRisotto turns the automation off and answers 429 "Automation exceeded its hourly event-run limit and was disabled" until you turn it back on.

Admin alerts

When a limit trips, Risotto posts a warning on the Alerts page and in your notifications channel, if you have one: Automation webhook deliveries rate limited (once per window, naming the automation whose call crossed it) or Automation disabled after too many runs (naming the automation and its run count, with a link).

Auth token

Every call must carry the token. Copy auth header copies the full line, Authorization: Bearer rsto_.... Risotto also accepts the token without Bearer , or in X-Risotto-Webhook-Auth-Token, but never in the URL.

  • Regenerate. In the editor, choose Regenerate… in the menu beside Copy auth header, confirm, and save. The old token stops working when you save. You can't remove the token.
  • Older automations. One saved before tokens were required shows None. Save the automation to generate one. and answers 401 to every call until you save it.
  • Audit. The audit log records each time the token is generated, regenerated or copied.
  • No signing. Risotto compares the token and doesn't verify the body or answer verification challenges. For a service that can't add a header, or that checks the URL first (such as the Slack Events API), put a relay in between, such as a small cloud function.

Okta triggers

The Okta submenu has Account created, Account activated, Account suspended, Account locked and Account deactivated, each recording the person's login, name and Okta ID, the actor, Okta's reason and the time. They need Automation triggers turned on for the Okta connection under Settings > Integrations > Okta; newer events are listed under Needs setup until you click Update subscriptions on the Okta card. See Okta Automation Triggers.

Rippling triggers

Employee created, Employee hired and Employee terminated, each recording the employee's work email, name, Rippling worker ID, the time, and the start or end date. Rippling sends them only for employees with access to Risotto within Rippling. See Rippling.

BambooHR triggers

Employee created, Employment status changed and Employee terminated, each recording the employee's work email, name, BambooHR employee ID and the time. They need the BambooHR webhook configured. See BambooHR.

HiBob triggers

Employee created, Employee joined and Employee left, each recording the employee's work email, name, HiBob employee ID, the time, and the start or end date. HiBob sends them through the Risotto app in its Marketplace, with no webhook to configure. See HiBob.

Workday events can't start an automation; use the Webhook trigger instead.

Slack triggers

Slack Connect invite requested runs once per invitee when a member asks to invite someone from outside your organization to a channel. It records the invite ID, the invitee's email, the requester and the channel; the Approve Slack Connect Invite Request and Deny Slack Connect Invite Request tools act on it. It needs Slack Enterprise Grid, the Slack Tools connector with an org-wide install, and the Slack setting that holds external invites for approval. Until the connector is ready, the picker lists the trigger as unavailable with the note "Slack Tools is not connected with an org-wide install, or does not send events to Risotto yet." and an Open Slack item that opens Settings > Integrations > Slack. See Slack Connect Invite Approval.

When a trigger cannot fire

If a trigger's connection doesn't send its events (for example, Automation triggers is off for Okta), Risotto won't create an automation on it, switch to it, or turn it on, and says why. If the connection stops after you save, the automation stays on but doesn't run: Next run in the list shows Not firing (hover for the reason), and its page shows This automation is not firing. Fix the connection to resume.

Changing the trigger

On the edit page, click the trash icon (Remove trigger) in the trigger card, pick a new trigger under Add trigger, and click Save. The change applies at once and the automation stays enabled. The old schedule or department filter is cleared.

Risotto refuses the save if the instructions or arguments use a field the new trigger doesn't record, for example "Ticket created doesn't record reason. Update those references below." A schedule records no fields; a webhook accepts any. Each run keeps the trigger that started it, shown as a badge in the run history, and a run from an earlier trigger can't be re-run.

Referencing trigger fields

Every trigger except a schedule records fields. Use them:

  • In the instructions. Type @ and pick a field from the trigger's section, such as Ticket escalated data. The agent sees the field's name and reads the value from the event; Risotto never pastes the value into your instructions, so ticket text can't change the agent's orders.
  • In a tool argument. Set an argument to a field in the Tools card. Risotto fills it in at run time, and the agent can't change it.
  • In a custom field on Create Ticket or Update Ticket.

A reference is stored as {trigger:/<path>}, such as {trigger:/requester_email}. Risotto refuses a field the trigger doesn't record when you save. At run time, if the event lacks a referenced value or it is null, the agent refuses the one tool that needs it and the run continues.

Tools available to the agent

Every automation has these built-in tools:

ToolWhat it does
Create TicketOpens a ticket, optionally with a title, requester name, department, assignee, custom fields, a runbook and a Slack DM. See Tickets an automation creates.
Update TicketChanges a ticket's title, status, assignee or custom fields.
List TicketsLists tickets newest first, filtered by status, requester, assignee or creation time.
Get TicketFetches up to 50 tickets by ID (such as IT-123): title, request text, status, priority (with whether Risotto's AI set it), requester and assignee, department, and created and modified times.
Knowledge Gaps ReportReads the latest knowledge-gaps report: unanswered-question themes and possibly stale documents.
Automation OpportunitiesReports what Risotto could still automate, ranked by how many tickets each would cover.

Insert any configured tool from your tool catalog with #. No built-in tool reads ticket comments or custom field values; for comments, use a script tool that calls risotto.get_ticket_comments.

To act on the person in the event, turn off Restrict to Requestor Only on the tool and pin its email argument (for example email_address) to a trigger field such as {trigger:/user_email} (Referencing trigger fields). The tool then acts on that email; if the call gives no email, it still fails with the same error. With the setting off, the tool acts on any user the call names, so if a runbook also uses the tool, add a second copy for the automation and keep the setting on in the runbook's copy. You can also use a script tool that takes the person as an input.

Setting a tool's arguments in advance

Click an argument pill in the Tools card to set it yourself (Set by author), or leave it to the agent (Set by agent). A value you set is added when the tool runs, so the agent can't change it; type @ in a text value to include a trigger field. Runbooks use the same editor: see Setting a tool's arguments in advance.

On Create Ticket and Update Ticket, custom_fields opens a field editor that lists your ticket fields by label; an empty one shows Agent decides. If dept_id is set to one department, only its fields are listed; otherwise they're grouped by department. For a field that isn't text, Set from trigger data beside it offers the trigger fields whose values fit. A field that was deleted or made inactive shows Unavailable field; clear it.

Approvals

Asks for approval decides which tool calls run on their own and which pause the run for an admin. The automation's page and side panel show the level.

CardRuns without a pausePauses the run
Always (default)Tools that only read, such as Get Ticket and List TicketsEvery tool that changes something, including Create Ticket and Update Ticket
Destructive changesReads, and non-destructive changes such as Create Ticket and Update TicketDestructive tools ("Deletes and revokes wait"), and tools set to Required approval or requester verification
NeverEverything, even tools that require approvalNothing
  • Org Admins and Managers cap the level under Settings > Assistant > Approval mode (Highest mode operators may choose): Read only allows only Always, Auto-accept changes adds Destructive changes, and Auto-accept everything allows Never. A card above the cap shows Your organization does not allow this., and the cap also applies at every run.
  • Automations created before this setting existed were set to Destructive changes.
  • The setting governs automations only. In a ticket or runbook, a tool set to Required approval still asks every time.

Approving a paused run

A run that needs a decision shows Awaiting approval in the run history and the automations list.

  1. Open the run

    Click the run under Run history on the automation's page.

  2. Approve or deny

    The Tool approval card shows the tool, the agent's rationale and the parameters; values you set carry Set by author. Click Approve or Deny. For several calls, decide each (or use Approve all or Deny all) and click Submit decisions.

The run resumes on the same transcript; a denied tool returns a refusal and the agent continues without it. Risotto records Decided by with the email and time. Only Org Admins can decide. If an argument set on the tool changes while the run waits, the approved call is marked not run, and the agent can ask again.

Tickets an automation creates

An automation has no department. Unless Create Ticket names one, intake classifies the ticket from its text. To send every ticket to one department, set dept_id on Create Ticket. Each run's page lists the tickets it created.

  • Slack DM. Set notify_via_dm to true (or leave it to the agent) to message the requester: "A new request has been created for you by an automation.", with the title and request. They can reply in its thread. If Risotto can't find them in Slack, it creates the ticket without a message.
  • Runbook. Mention a runbook with @ and tell the agent to create the ticket with it; Create Ticket sets runbook_id, and the support agent follows that runbook instead of matching one. With a DM, this collects a form from someone other than the person in the event, such as a hiring manager named in a webhook call from a Jira rule.

Running an automation manually

Run Now and Re-run start a Manual run, also on a disabled automation, with the current instructions. The actions are real.

Run Now is under Actions on the automation's page and in each row's menu in the list:

  • Schedule: confirm Run automation now?. The schedule doesn't change.
  • Ticket, Okta, HR and Slack triggers: the dialog shows each field the trigger records, filled with sample data (such as IT-123, "New laptop request" for Ticket created). Edit them, or click Edit as JSON, then Run Now.
  • Webhook: a JSON editor with the newest body Risotto has (from Listen or a run), or {}.

Risotto checks the event like a real one: unknown fields are dropped (a webhook keeps the whole object), and a wrong type or missing required field stops the run with a message naming it.

Re-run

Click Re-run in a run's side panel or in its row menu under Run history, then Confirm. The new run reuses the earlier run's event and ticket with the current instructions and tools, so actions can repeat; the dialog warns Instructions changed if they were edited since. The new run's side panel links back under Re-run of. Re-run is disabled with Needs the event its trigger records or Trigger changed since this run; use Run Now instead.

Run history

Run history on the automation's page lists runs newest first, 10 per page: Run, Status (Queued, Running, Awaiting approval, Success or Failed), Kind (Scheduled, Event or Manual), Tickets and Result. A run's page shows:

  • Event: the recorded fields, or a webhook's body, with the ticket that fired it.
  • Instructions: what the run started with, kept even if the automation is edited while it waits.
  • Result (the agent's summary) or The run failed with the error.
  • Transcript: the agent's steps, with an approval card for each pause.
  • In the side panel: Status, Trigger, Fired, Started, Duration, Triggered by, Re-run of and Tickets created.

Managing automations

Each row's menu has Edit, Run Now, Activate or Deactivate, Duplicate and Delete; the automation's page has the Enabled switch, Edit, and the same actions under Actions.

  • Disable keeps the definition and history; the automation stops firing.
  • Duplicate creates a disabled copy with "(copy)" after the name.
  • Delete stops the automation immediately. Tickets it created are unaffected.

You can also ask the Assistant to create, change, turn on or off, and run an automation, approving each action. Deleting, duplicating, webhook triggers, the Never level and decisions on paused runs stay in the dashboard.

Troubleshooting

The automation doesn't run

  • Check Enabled; a disabled automation shows Disabled under Next run.
  • Not firing under Next run means the trigger's connection isn't sending events. Hover it for the reason (When a trigger cannot fire).
  • A ticket trigger fires only for its departments, and never for a ticket an automation created.
  • A webhook call answered 401 lacks the right auth header; 404 means the URL no longer starts this automation.

The automation turned itself off

It started more than 75 event runs in an hour. Check the Automation disabled after too many runs alert, wait for the burst to end, and turn it back on.

A run stays at Awaiting approval

A tool call is waiting for an Org Admin. Approve or deny it on the run's page, or pick a less strict approval level.

Save fails with "doesn't record"

The instructions or an argument use a field the trigger doesn't record. Change those references, or pick a trigger that records the field.

Something wrong or missing? Report an issue · View as Markdown