Ticket actions
Create ticket
Create ticket
- Workspace and Channel - Where the ticket is created
- Title, Description, Status, Priority, and Type
- Requester and Author - Who the ticket is for, and who it is recorded as coming from
- Assignee, Followers, Tags, Category, and Due date
- Approvers - Set on the ticket at creation, so the approval is in place before anyone opens it
- Parent ticket - Links the new ticket as a child at creation time. The parent does not have to be in the same workspace as the child.
- Form - The form to attach, and its field values
- Ticket attributes - Values for the workspace’s custom fields
ticketId- The ID of the created ticketisSuccess- Boolean indicating whether creation succeeded
- Create follow-up tickets for multi-step processes
- Generate tickets from Slack messages or external events
- Hand off work to another team’s workspace and let their automations pick it up
- Fan one intake event out to a child ticket per team, all linked to a shared parent
Update Ticket
Update Ticket
- Escalate tickets by changing priority
- Update custom fields based on workflow logic
- Set a parent ticket to organize tickets into a hierarchy
- Reassign the requester when a ticket is submitted on behalf of someone else
Publish Ticket
Publish Ticket
- Create and configure a ticket across multiple steps before making it visible
- Control when notifications are sent for new tickets
Set Status
Set Status
- Auto-resolve tickets meeting specific criteria
- Move tickets through workflow stages
Set Priority
Set Priority
- Escalate urgent issues automatically
- Adjust priorities based on SLA requirements
Set Type
Set Type
type- The type the ticket was set to
- Reclassify a request as an incident when a Custom Prompt or AI Decision Maker flags an outage
- Set the type from a form answer
Add Assignee
Add Assignee
- User - Assigns the user you choose.
- Round Robin - Picks one person from a list of users or groups in rotation, to balance workload. Groups are expanded into their members when the workflow runs.
- Random - Picks one person from the list at random.
- Distribute tickets across a group with Round Robin for load balancing
- Route tickets to a specific owner based on form or channel
- Stage multiple Round Robin assignments (triage, then review) in one workflow
Add Followers
Add Followers
- Add managers to high-priority tickets
- Include cross-functional stakeholders
Move Ticket
Move Ticket
- Transfer tickets between teams
- Escalate to a different department’s workspace
Send Message
Send Message
- Message Type: Who sees the message. Defaults to Public.
- Public: Everyone on the ticket sees the message.
- Private: Only your team sees the message, as a private note.
- DM: Ravenna sends the message to one person about the ticket.
- Recipient: The user who receives the DM. Required when Message Type is DM.
- Send automated updates to requesters
- Request additional information
- Message an approver, manager, or new hire directly about a ticket
Link Ticket
Link Ticket
ticketId- The Ravenna ticket to attach the link toname- Descriptive name for the link, such as “Related Jira Issue”url- The external URL to link to
isSuccess- Boolean indicating whether the link was createdticketLinkId- The ID of the created ticket linkticketId- The ID of the linked ticketurl- The URL that was linked
- Link to issues in Jira, Linear, or GitHub created earlier in the workflow
- Reference Slack channels created for incidents
Apply Task Template
Apply Task Template
- Attach onboarding checklists to new hire tickets
- Apply standard operating procedures to incident tickets
Complete Tasks
Complete Tasks
completedTaskItemIds(Completed Tasks) - The tasks that were marked complete
- Check off a checklist item after an approval is granted
- Close out remaining tasks when a ticket is resolved
Search Tickets
Search Tickets
- Ticket Filter: One or more filter groups on ticket properties. Groups combine with OR, and conditions inside a group combine with AND.
- Limit: Maximum number of tickets to return (1 to 50, default 50).
ticketIds(Ticket search results) - Array of matching ticket IDs
- Find related or duplicate tickets
- Check for existing tickets before creating new ones
- Pair with a Cron trigger and a Loop for scheduled clean-ups
Search Users
Search Users
- User Filter: One or more filter groups on user attributes such as name, email, or group membership. Groups combine with OR, and conditions inside a group combine with AND.
- Limit: Maximum number of users to return. Set a value from 1 to 10, or leave it empty to return up to 50.
userIds- Array of user IDs matching the filter
- Look up the members of a group or team to notify or assign
- Build a dynamic recipient list for Add Assignee, Add Followers, or Send Email
- Combine with Loop to run actions per matching user
Start Lifecycle
Start Lifecycle
- Start onboarding when the Employee Hired trigger fires
- Start a lifecycle from a webhook sent by another system
Approval actions
Pair an approval action with Wait for Approval to pause the workflow until a decision is made.Add Approval Round
Add Approval Round
- Approvers (required) - Users or groups who can approve
- Approval Policy - Any can approve (default), All must approve, or Majority must approve
- Assignment Strategy:
- All (default) - Every selected approver is added to the round.
- Round Robin - One approver is picked from the list in rotation.
- Auto Approve - The ticket is approved immediately by the workspace bot. If the ticket already has an approval round in progress, the step adds every listed user instead, as if you had chosen All.
approverIds(Approvers) - The approvers added to the round
- Require a manager’s approval, then a second team’s approval, by adding one round after another
- Auto-approve low-risk requests on one branch and require approval on another
Apply Approval Template
Apply Approval Template
ticketId- The ticket the template was applied toapprovalTemplateId- The template that was applied
- Apply the same multi-round approval process to every request of a given type
- Pick a template per department with If / Else
Add Approvers
Add Approvers
Wait actions
Wait actions pause the run. While a run is paused, it shows as waiting in the run log.m (minutes), h (hours), d (days), w (weeks), or y (years), such as 30m, 8h, or 2d. Where a step allows it, type Forever to wait with no time limit.Wait
Wait
- Duration - How long to wait. Defaults to
8h. AcceptsForever, and relative durations like1d - 8h. - From Date (optional) - The date to count from. Defaults to the time the step runs.
- Timezone (optional) - The timezone used for the calculation.
- Add a delay between actions
- Create timed follow-ups
Wait Until
Wait Until
- Target Date - A fixed date or a dynamic value, such as a date field from a form.
- Time - The time of day to continue on the target date.
- Timezone - The timezone for that time.
- Date Offset (optional) - Moves the target earlier or later. A positive offset such as
5dwaits until after the date. A negative offset such as-5dwaits until before it, so-5don an onboarding date of March 20 continues on March 15.
- Send reminders before a deadline or renewal date
- Start onboarding tasks relative to a start date
- Revoke temporary access on its end date
Wait for Approval
Wait for Approval
- Duration - Maximum time to wait. Defaults to
3d. If it passes without a decision, the workflow continues down On Timeout.
isApproved- Boolean indicating whether the ticket was approvedisTimedOut- Boolean indicating whether the wait expired before a decisionapprovedByUserIds(Approved By) - Array of user IDs who approved the ticket, across all of its approval roundsdeclinedByUserIds(Declined By) - Array of user IDs who declined the ticket, across all of its approval rounds- Force Approved By - The user who force-approved the ticket, if anyone did
- On Approved runs when the ticket is approved.
- On Declined runs on an explicit decline only.
- On Timeout runs when the duration passes before anyone decides. Use it to escalate, notify the requester, or close the ticket.
- Gate access provisioning until approved
- Notify the requester when a request is declined
- Escalate stalled approvals
Wait for Message
Wait for Message
- Message Authors (required) - Users or groups whose messages resume the workflow
- Duration - Maximum wait time. Defaults to
3d. - Message Sources (optional) - Web, Email, or Slack. Leave empty to accept every source.
isSuccess- Boolean indicating whether a matching message arrived before the timeoutticketMessageId- The message that resumed the workflow, when one arrived
- Wait for a requester’s reply before continuing
- Pause until a specific team member provides input
Wait for Inactivity
Wait for Inactivity
- Duration - How long the ticket must stay quiet. Defaults to
8h. - Users (optional) - Only count messages from these users. Leave empty to count messages from anyone.
- Auto-resolve tickets after a quiet period
- Send a reminder before auto-closing
Monitor Ticket
Monitor Ticket
- Duration - How long to keep watching. Defaults to
8h. - Optional Filters - The ticket state to wait for. Unlike other actions, these conditions don’t skip the step; the step waits until they match.
isSuccess-trueonce the conditions match
- Wait for a ticket to reach a status before continuing
- Continue only after an assignee or field is set
AI Conversation Monitor
AI Conversation Monitor
- Duration - How long the thread must be quiet. Defaults to
24h.
- Follow up with the requester after the agent’s conversation goes quiet
Control flow actions
Conditional
Conditional
Conditional > Is Success- Boolean indicating whether the conditions matched
- Run one action if any of several checks match, with one Conditional per check feeding that action
- Save a check’s result for a step further down the workflow
If / Else
If / Else
Is Success- Boolean indicating whether the conditions matched
- Do different things depending on ticket properties, such as priority or form answers
- Stop a path entirely when a check fails
Goto
Goto
- Step - The earlier step to jump to.
- Budget - How many times the jump can happen in one run. Defaults to 1, maximum 100. Once the budget is used up, the workflow continues down On Limit Reached instead of jumping.
- Retry a check after a wait, such as polling an external system until it is ready
- Re-send a reminder a fixed number of times
Loop
Loop
- Array outputs from earlier steps, such as
ticketIdsfrom Search Tickets oruserIdsfrom Search Users. - Multi-value custom fields on the ticket’s form, including Multi-Select, User Multi-Select, Multi-Application Select, and Tag Select fields. Reference the field like any other form value and pick it as the loop’s collection.
item. For entity multi-selects the item is the underlying ID (for example, a user, application, or tag ID), which actions like Add Assignee, Add Followers, or Update Ticket accept directly. For a generic Multi-Select the item is the selected option as text.Common use cases:- Process each result of a search
- Send notifications to a list of users
- Act on each member, application, or tag a requester selected on the intake form
AI actions
Summarize
Summarize
- Generate ticket summaries for handoffs
- Summarize resolution steps
AI Decision Maker
AI Decision Maker
- Route tickets based on content analysis
- Evaluate sentiment for escalation
Custom Prompt
Custom Prompt
- Prompt - Instructions for the AI. Insert dynamic values from earlier steps to pass in data.
- Ticket (optional) - A ticket to include as context, such as the trigger ticket.
- AI Response - The AI’s answer, available to later steps.
- Outputs - Structured values Ravenna infers from your prompt, such as a category or a yes/no decision, so later steps can reference each one directly.
- Draft response messages based on ticket content
- Extract structured data from unstructured text
- Analyze sentiment or urgency from messages
Messaging actions
Send Email
Send Email
- Existing followers, approvers, the requester, assignee, and author are skipped.
- Email addresses that don’t match a Ravenna user are ignored.
- Followers are not added when the ticket is private.
- If adding followers fails, the email is still sent and the error is logged.
- When a verified email domain exists and Sender Address is set, Ravenna sends from
<localPart>@<verified-domain>. The action does not offer a domain picker. - When Sender Address is blank, Ravenna uses the organization-level sender address from Organization Settings > Email, if one is configured.
- When the workflow runs on a ticket, Ravenna sets Reply-To to the ticket’s address (
ticket+<id>@…) so replies thread back to the same ticket. - When no verified email domain exists, Ravenna sends from the default support sender (
support@<ravenna-inbound-domain>) for sends without a ticket, or from the ticket’s address when running on a ticket.
- Notify external stakeholders who are not in Slack
- Send formal communications like approval confirmations or access grants
- Deliver summary reports or status updates by email
Send Form
Send Form
- Unlocked (default): the value is a starting point and the recipient can change it.
- Locked: the field is read-only for the recipient. Fields you did not pre-fill stay editable.
FORM_LOCKED_FIELD_CHANGED. You can only lock fields you also pre-fill.Email delivery:With Email, Ravenna emails the recipient a link to the pre-filled form. A form request bypasses the recipient’s “messages” notification preference, so it arrives even if they’ve muted general ticket messages. If the ticket is not private, the recipient is also added as a follower.Common use cases:- Collect required details before continuing
- Send a targeted form to an approver or hiring manager over email
- Pre-fill known fields and lock them, while asking the recipient for the rest
Send CSAT
Send CSAT
- Survey after ticket resolution
- Measure service quality
Access actions
Find these actions under the Access group in the action picker.Search Entitlements
Search Entitlements
- Entitlement Filter: One or more filter groups on Application, User, or Status. Groups combine with OR, and conditions inside a group combine with AND.
- Limit: Maximum number of entitlements to return (default 100, maximum 500).
synthetic-. Later steps can resolve these IDs like any other entitlement ID.Output data:entitlementIds- Array of entitlement IDs matching the filteruserIds- Array of users holding the matched entitlements. Each user appears once, even if they hold several matching entitlements.
- Run a periodic access sweep with a Cron trigger
- Pipe
userIdsinto bulk user actions, such as the Okta Deactivate User or Remove Users from Groups actions - Notify the holders of an application’s access with Send Email, Add Followers, or Loop
Revoke Entitlement
Revoke Entitlement
- Entitlements: The entitlements to revoke. Reference the
entitlementIdsoutput of Search Entitlements, or the entitlement from an Entitlement Status Changed trigger. - Revoke Note (optional): Why the entitlements were revoked.
entitlementIds(Revoked Entitlements) - Array of the revoked entitlement IDs
- Clean up stale access on a schedule with Cron and Search Entitlements
- Revoke access during offboarding
Asset actions
Create, update, find, and assign assets. Find these actions under the Asset group in the action picker.Create Asset
Create Asset
- Name and Asset Type - Required
- Description (optional)
- Status (optional) - Defaults to the organization’s default status
- Assignees (optional) - Users or user groups to assign. User groups are expanded into their members.
assetId(Created Asset) - The ID of the new asset
- Record hardware ordered through a procurement request
Update Asset
Update Asset
- Asset - The asset to update
- Asset Type, Name, Description, and Status (optional)
- Assignees (optional) - Replaces the asset’s current assignees with the selected users
assetId(Updated Asset) - The ID of the updated asset
- Move an asset to In Repair when a repair ticket is opened
- Hand an asset to a new holder in one step
Archive Asset
Archive Asset
- Asset - The asset to archive
assetId(Archived Asset) - The ID of the archived asset
Search Assets
Search Assets
- Asset Filter: One or more filter groups. Under Asset Type, open a type to filter on that type’s custom fields.
- Limit: Maximum number of assets to return (default 50, maximum 50).
assetId- The matching asset, when Limit is 1assetIds- Array of matching asset IDs, for any other limit
- Find every asset a departing employee holds, then reassign them with Assign Asset
- Pair with a Cron trigger to review assets in a given status
Assign Asset
Assign Asset
- Assets - One or more asset IDs. Pass a single ID, a list, or a reference resolving to either, such as the
assetIdsoutput of Search Assets. - Strategy - How to apply the change:
- Add assignees adds the selected users to each asset’s current assignees.
- Remove assignees removes the selected users from each asset.
- Set assignees replaces each asset’s assignees with exactly the selected users.
- Clear removes every assignee.
- Users - The users to add, remove, or set. Not needed for Clear. User groups are expanded into their members. Set assignees needs at least one user, and the step fails if the selected users and groups resolve to nobody.
assetIds- The IDs of the assets that were updated
- Assign new hardware to an employee when an onboarding ticket is submitted
- Clear assignees when an asset is returned to inventory
Tool actions
HTTP Request
HTTP Request
- URL - The API endpoint to call
- Method - GET, POST, PUT, DELETE, or PATCH
- Headers - Custom key-value headers
- Query Parameters - Key-value pairs appended to the URL
- JSON Body - Request body (for POST, PUT, PATCH, DELETE)
- Timeout - Seconds to wait for a response. Defaults to 10, maximum 45.
- Fail on error - Whether the step fails when the call fails. On by default. When off, the workflow continues with
isSuccessset tofalseand the error inResponse.Error. - Signature - Optional HMAC-SHA256 signing for outbound webhooks (see below)
- None - No authentication
- API Key - Sends a key in a configurable header (default
X-API-Key), from a vault credential. - Bearer Token - Sends a token in the
Authorization: Bearerheader, from a vault credential. - Basic Auth - Sends a username and password as a Base64-encoded
Authorization: Basicheader. The password supports vault credentials.
- Signing Key - A vault credential holding the shared secret, encrypted at rest and decrypted in memory at request time.
- Signature Header - The header that carries the signature. Defaults to
X-Ravenna-Signature.
HMAC-SHA256(body, secret), hex-encodes it, and sends it in the header. The signature covers the request body only, not the headers, URL, method, or query parameters. Requests without a body are sent without a signature. The receiver computes the same HMAC over the raw body with its copy of the secret and compares it to the header.Output data:isSuccess- Boolean indicating whether the response status code is 2xxResponse.Body- The response bodyResponse.StatusCode- The HTTP status codeResponse.Error- The error message when the call fails and Fail on error is off
isSuccess: false, Response.StatusCode: 500, and the error in Response.Error, so later steps can branch on the result, for example with an If / Else on isSuccess that posts Response.Error to Slack.Common use cases:- Send data to external systems
- Fetch information from third-party APIs
- Integrate with services that lack a native Ravenna integration
Content-Type: application/json only when the request has a body. A GET, or a DELETE with an empty body, goes out with no Content-Type. Set the header yourself under Headers if an API needs it regardless.my_ticket_id produces a working URL.