Ticket triggers
Ticket Created
Ticket Created
- Auto-assign tickets based on form or channel
- Send welcome messages to requesters
- Notify team members of new tickets
- Route tickets to specialized teams
Form Submitted
Form Submitted
- Fires when a ticket is created with form data
- Fires when form field values are updated on existing tickets
- Route tickets based on submitted form type
- Trigger approval workflows for access request forms
- Send notifications when specific forms are submitted
- Email a submitted form’s answers to a person or team with a Send Email step
Category Assigned
Category Assigned
- Fires when a ticket is created with a category
- Fires when a category is changed on an existing ticket
- Route tickets based on assigned category
- Auto-assign tickets from specific categories to specialized teams
- Escalate tickets when high-priority categories are assigned
Ticket Archived
Ticket Archived
- Clean up related Slack channels
- Send final status notifications
- Update external tracking systems
Ticket Assigned
Ticket Assigned
- Notify assignees of new assignments
- Update workload tracking systems
- Send assignment confirmation messages
Ticket Status Changed
Ticket Status Changed
- Send notifications on status changes
- Update external systems when tickets are resolved
- Trigger follow-up workflows based on status
Ticket Approval
Ticket Approval
ticketId- The ID of the ticket whose approval status changedisApproved- Boolean indicating whether the ticket was approvedapprovedByUserIds(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
- Continue workflows after approval
- Notify stakeholders of decisions
- Provision access after approval
- Handle declined requests
SLA Outcome Changed
SLA Outcome Changed
- SLA Attached - An SLA is first applied to a ticket. Use this to acknowledge the commitment or notify stakeholders.
- SLA Alert - An SLA alert threshold is crossed, before a breach. Use this for early warnings and escalations.
- SLA Breached - An SLA target is missed. Use this for escalation, reassignment, or stakeholder notifications.
- SLA Met - An SLA target is met. Use this for confirmation messaging or reporting.
ticketId- The ID of the ticket whose SLA outcome changed
- Escalate tickets and notify managers when an SLA is breached
- Send early-warning pings to assignees on SLA alerts
- Confirm to requesters when SLA commitments are met
- Apply tags or update priority when an SLA is attached
Reminder Expired
Reminder Expired
- Reminder Type (optional): Limit the trigger to one reminder type. Leave empty to fire on any reminder. Supports , , and . These are scheduled automatically when an approver or assignee has not acted within the configured window, or when an SLA alert fires.
ticketId- The ID of the ticket the reminder was attached toreminderType- The type of reminder that expired (Approval,Assignment, orSLA)
- Nudge approvers in Slack or email when an approval reminder fires
- Reassign or escalate a ticket when an assignment reminder fires
- Escalate to a lead or raise priority when SLA reminders run out before the target is met
- Post a private note on the ticket summarizing pending approvers
Entitlement Status Changed
Entitlement Status Changed
- Statuses (required): Select one or more entitlement statuses. One trigger can cover several outcomes, so you do not need a workflow per status.
- Processing - Provisioning or deprovisioning has started. For manual access levels this is the point at which someone needs to grant access.
- Access Provisioned - The user was granted access.
- Access Deprovisioned - The user’s access was removed.
- Provision Failed - Granting access failed.
- Deprovision Failed - Removing access failed.
- Skipped Provisioning - Provisioning was skipped, for example because the user already had access.
- Skipped Revocation - Revocation was skipped, for example because another active grant still requires the access.
ticketId- The ID of the access request ticket that owns the entitlemententitlementId- The ID of the entitlement whose status changed. Expand it to readapplicationId,accessLevelId,userGroupId,userId, andentitlementStatus.
- Notify the requester when their access is provisioned
- Alert the IT team when provisioning or deprovisioning fails
- Cover Access Provisioned, Deprovision Failed, and Skipped Provisioning in one workflow
Task triggers
Task Item Completed
Task Item Completed
- Task Template - Only fire for tasks imported from this template. Once a template is selected, you can also pick one task from it.
- Task Name - Only fire for tasks whose name contains this text (case-insensitive)
- Assignees - Only fire for tasks assigned to at least one of these users
ticketId- The ID of the ticket containing the tasktaskItemId(Task Item Completed) - The ID of the completed tasktaskDescription(Task Name) - The name of the completed taskcompletedByUserId(Completed By) - The user who completed the task, or the workspace bot when a workflow completed itcompletedAt(Completed At) - When the task was completed
- Notify a stakeholder when a specific checklist item is done
- Complete or close the ticket once the last required task is checked off
- Hand off to the next team when their prerequisite task is completed
Task Template Applied
Task Template Applied
ticketId- The ID of the ticket the template was applied totaskTemplateId- The template that was applied
- Notify assignees when a task template is applied
- Trigger onboarding or checklist workflows
- Set ticket status or priority based on the applied template
Lifecycle triggers
Lifecycle Step
Lifecycle Step
- Order a laptop or create accounts when an onboarding step opens
- Use a new hire’s form answers in a request to another system
Lifecycle Completed
Lifecycle Completed
- Post a summary when onboarding finishes
- Close the lifecycle’s parent ticket
Employee Hired
Employee Hired
- Start an onboarding lifecycle with the Start Lifecycle action
Employee Leaving
Employee Leaving
- Start an offboarding lifecycle with the Start Lifecycle action
Message triggers
Message Sent
Message Sent
- Message Authors (optional): Limit the trigger to messages from specific users or groups.
- Visibility (optional): Restrict the trigger to
PublicorPrivatemessages. Leave unset to fire on both.- Public: Messages visible to requesters and external channels.
- Private: Internal-only private notes that stay hidden from requesters.
- Filters (optional): Match on other message or ticket attributes.
ticketId- The ticket the message was added toticketMessageId- The message that was added
- Analyze message content or sentiment
- Notify team members of updates
- Trigger automated responses
- Route only public replies to customer-facing workflows, or only private notes to internal review flows
Asset triggers
Fire when an asset changes. Each asset trigger accepts an optional Asset Type filter. Leave it empty to fire for every asset type. In a workspace’s workflows, asset type options on triggers and actions list the asset types linked to that workspace.Asset Created
Asset Created
assetId- The ID of the asset that was createdactorId(Actor) - The user who made the change
- Open a setup ticket for new hardware
Asset Updated
Asset Updated
assetId- The ID of the asset that was updatedactorId(Actor) - The user who made the change
- Open a repair ticket when an asset moves to an Unavailable status
- Sync status changes to an external inventory system
Asset Archived
Asset Archived
assetId- The ID of the asset that was archivedactorId(Actor) - The user who made the change
- Record disposal of retired hardware in an external system
Asset Assignment Changed
Asset Assignment Changed
assetId- The asset whose assignees changedactorId(Actor) - The user who made the change- Assignees -
addedholds the user who was assigned andremovedholds the user who was unassigned. Each run fills one of the two. currentAssigneeIds- Everyone who holds the asset after the change
- Notify IT when a laptop is assigned to someone
- Start a return process when a laptop is unassigned, with a condition that Current Assignees is empty so a direct handover to someone else skips the return
Scheduled triggers
Cron
Cron
- Schedule - A standard 5-field cron expression (
minute hour day-of-month month day-of-week). Use the inline picker to build common schedules, or type an expression directly. Examples:0 * * * *- Every hour, on the hour.0 9 * * 1-5- 9:00 AM, Monday through Friday.0 0 1 * *- Midnight on the first day of each month.*/15 * * * *- Every 15 minutes.
- Timezone - The timezone the schedule runs in. Defaults to UTC.
- Schedule recurring reports or cleanup tasks
- Automate periodic ticket reviews
- Run time-based processes
Webhook triggers
Webhook Trigger
Webhook Trigger
- Add the Webhook Trigger to a workflow.
- Copy the Direct URL and set it as the destination in the system that sends the webhook.
- Write a Prompt that describes how to turn the incoming payload into the fields you need.
- Publish the workflow. When the external system posts to the URL, Ravenna runs the prompt against the request body and starts the workflow with the parsed output.
- Direct URL - Read-only URL to register with the sending system. Click to copy.
- Prompt - Instructions for turning the webhook body into structured data for later steps.
- Ticket (optional) - A ticket to give the prompt as extra context.
- Webhook response HTTP Status Code - The status code Ravenna returns once the run is accepted:
200(default),201,202, or204. Some webhook providers retry or disable the endpoint when they get an unexpected status, so pick the code their documentation specifies.
- Only published workflows run. A request to a draft or turned-off workflow is rejected.
POSTrequests start a run, and the response body contains the run ID. Other requests, such as health checks, get a200without running the workflow.- Request bodies can be up to 10 MB.
- Endpoint verification handshakes are answered automatically, without running the workflow, so you can register the URL with Okta event hooks, Slack Events API, Microsoft Graph subscriptions, Meta webhooks, and providers that echo a
challengeparameter.
token query parameter and does not need API keys, signatures, or extra headers. Treat the whole URL as a secret: anyone who has it can start the workflow while it is published.- Store the URL in the sending system’s secret manager rather than in shared documents or public code.
- If the sending system supports it, restrict its egress by IP allowlist.
- Receive events from systems without a native Ravenna integration
- Bridge custom internal tools into workflow automation
- Trigger workflows from monitoring or alerting platforms
Slack triggers
Slack triggers appear under the Slack tile in the trigger picker once the Slack integration is connected.Reaction and member triggers
Reaction and member triggers
- Reaction Added and Reaction Removed fire when someone adds or removes an emoji reaction in the channels you choose, optionally for one emoji.
- User Joined Channel, User Left Channel, and User Joined Team fire on Slack membership changes.
AI Start Conversation Trigger
AI Start Conversation Trigger
- Slack workspace, Slack channel, and Slack thread of the conversation
userId- The Slack user who started the conversationticketId(Tracking ticket) - The ticket tracking the conversation
- Follow up on agent conversations with an AI Conversation Monitor step
- Log or tag tickets the agent picked up
AI Feedback Trigger
AI Feedback Trigger
- Feedback type - Negative (default) or Positive.
- Slack workspace, Slack channel, and Slack thread where the feedback was given
- Feedback received -
positiveornegative
- Escalate a conversation to a person after negative feedback
- Track positive feedback for reporting