Who does what
Ravenna coordinates
Intake, tickets, the cross-team handoff, checklists, approvals, notifications, and the audit trail.
Your provider provisions
Add someone to a group in Okta, Google Workspace, or Entra ID and it assigns every application mapped to that group.
Learn more about choosing a provisioning method
Pick your pattern
Only the first step differs, so you can change the trigger later without touching the rest.
Three ways in
Prefer the first one your stack supports.- HRIS webhook
- Alert channel
- Ravenna form
Webhook (AI Prompt Trigger) gives you a URL to register with your HRIS and a prompt that pulls the fields out of whatever it sends, so the payload shape is not your problem.This is the strongest option because it acts the moment the event happens. HRIS employee data syncs every 24 hours, so a webhook is what buys you a full day of lead time to ship a laptop.
The employee record
Capture the same fields whichever intake you use, because every branch downstream reads them.One parent, one child per team
Give the work the same shape as your org: a parent ticket in the workspace of the team that owns the event, and a child ticket in each team that has a part in it. Creating a child fires that team’s own workflow, so each team owns and maintains their half.The parent answers “where is this up to”. The children are where the work happens. People Ops owns the parent when both teams are on Ravenna, otherwise whichever team is.Building the fan-out
One Create Ticket step per team does all of it:Create Ticket also sets requester, assignee, followers, category, tags, due date, and status, so the child arrives already routed.
Ticket attribute pickers list the workflow’s own workspace, so send destination-specific values through the copied form or the description. Update Ticket works within its own workspace, so set what you need on the create.
Learn more about Create Ticket
Let Copilot build it
Describe the end state and Copilot returns a plan before it creates anything:When the New hire form is submitted in the People Ops workspace, create a child ticket in the IT workspace, one in Facilities, and one in Finance. Set each child's parent to the ticket that triggered the workflow, and set each child's form to the New hire form so the field values carry across.
Learn more about building automations with Copilot
Where teams get this wrong
One workflow doing every team's work
One workflow doing every team's work
Give each team a child ticket and let them own the workflow it triggers.
Child tickets created without the form
Child tickets created without the form
Set the Form input, or every responder opens two tickets and the child’s workflow has no fields to branch on.
An intake rule that talks back
An intake rule that talks back
Add “do not reply in the channel” to the rule and the agent files the ticket quietly.
Dates with times on them
Dates with times on them
Every scheduled step drifts by a day for someone. Use date-only fields.
Waiting for the HRIS sync
Waiting for the HRIS sync
It runs every 24 hours. To act on the day of the event, intake has to be a webhook, an alert, or a form.
Next
Employee onboarding
Build the joiner side, timed off the start date.
Employee offboarding
The same machinery in reverse, with a real deadline.