Skip to main content
Every workflow starts from exactly one trigger. The trigger listens for an event, and its data is available to every step after it. Narrow a trigger with its own options, such as forms or statuses, and with filters. Filters inside a group must all match, and separate groups need only one to match, the same as conditions.

Ticket triggers

Fires when a ticket is created. Optionally choose forms so the trigger fires only for tickets created from them, and add filters on channel, priority, or any other ticket field.Common use cases:
  • Auto-assign tickets based on form or channel
  • Send welcome messages to requesters
  • Notify team members of new tickets
  • Route tickets to specialized teams
Fires when a form is submitted, and again when form values are updated on an existing ticket. Choose at least one form.Trigger behavior:
  • Fires when a ticket is created with form data
  • Fires when form field values are updated on existing tickets
The selected forms’ fields become in later steps.Common use cases:
  • 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
Fires when a category is assigned or changed on a ticket. Choose at least one category.Trigger behavior:
  • Fires when a ticket is created with a category
  • Fires when a category is changed on an existing ticket
Common use cases:
  • Route tickets based on assigned category
  • Auto-assign tickets from specific categories to specialized teams
  • Escalate tickets when high-priority categories are assigned
Fires when a ticket is archived. Use this to clean up related resources or send final notifications.Common use cases:
  • Clean up related Slack channels
  • Send final status notifications
  • Update external tracking systems
Fires when a ticket is assigned to a user.Common use cases:
  • Notify assignees of new assignments
  • Update workload tracking systems
  • Send assignment confirmation messages
Fires when a ticket moves to one of the statuses you choose. Select one or more Statuses, and add filters for anything else, such as channel or assignee.Common use cases:
  • Send notifications on status changes
  • Update external systems when tickets are resolved
  • Trigger follow-up workflows based on status
Fires when tags are added to or removed from a ticket. Optionally choose tags to watch.Output data:
  • ticketId - The ID of the ticket that was updated
  • action.added - Array of tag IDs that were added
  • action.removed - Array of tag IDs that were removed
Common use cases:
  • Escalate tickets when priority tags are added
  • Notify teams when specific tags are applied
  • Auto-assign tickets based on tag changes
Fires when a ticket is approved or declined.Output data:
  • ticketId - The ID of the ticket whose approval status changed
  • isApproved - Boolean indicating whether the ticket was approved
  • approvedByUserIds (Approved By) - Array of user IDs who approved the ticket, across all of its approval rounds
  • declinedByUserIds (Declined By) - Array of user IDs who declined the ticket, across all of its approval rounds
Reference Approved By and Declined By in later steps to act on the people who made the decision. For example, mention the approver in a Slack message, notify the decliner by email, or iterate over each approver with a Loop. The decline reason is posted on the ticket automatically. See decline reasons.Common use cases:
  • Continue workflows after approval
  • Notify stakeholders of decisions
  • Provision access after approval
  • Handle declined requests
Learn more about approvals in workflows
Fires when an SLA target changes state on a ticket. Each target (first response, resolution, or close) fires on its own, so a ticket with three targets can start the workflow up to three times for the same status.Status options:
  • 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.
Output data:
  • ticketId - The ID of the ticket whose SLA outcome changed
Common use cases:
  • 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
Fires when a scheduled reminder on a ticket reaches its fire time. Use this to drive follow-up automations when a ticket has been sitting without the expected action.Configuration:
  • 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.
Output data:
  • ticketId - The ID of the ticket the reminder was attached to
  • reminderType - The type of reminder that expired (Approval, Assignment, or SLA)
Common use cases:
  • 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
Fires when an entitlement changes status. An entitlement is an individual access grant to a user for a specific user group, created when an access request is approved.Configuration:
  • 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.
Output data:
  • ticketId - The ID of the access request ticket that owns the entitlement
  • entitlementId - The ID of the entitlement whose status changed. Expand it to read applicationId, accessLevelId, userGroupId, userId, and entitlementStatus.
Common use cases:
  • 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

Fires when any task on a ticket is marked complete: tasks from a task template, tasks sent by a workflow or Ravenna Assistant, and tasks added by hand. It fires no matter where the task was completed.Filters (all optional):
  • 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
Output data:
  • ticketId - The ID of the ticket containing the task
  • taskItemId (Task Item Completed) - The ID of the completed task
  • taskDescription (Task Name) - The name of the completed task
  • completedByUserId (Completed By) - The user who completed the task, or the workspace bot when a workflow completed it
  • completedAt (Completed At) - When the task was completed
Common use cases:
  • 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
Fires when a task template is applied to a ticket. Optionally choose one template.Output data:
  • ticketId - The ID of the ticket the template was applied to
  • taskTemplateId - The template that was applied
Common use cases:
  • 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

Fires when a lifecycle’s Workflow step opens. Choose the Template and the Step: a Workflow step whose ticket opens in this workflow’s workspace. One active workflow runs each step, and the step completes when its ticket closes, so the workflow should close the Step ticket. A workflow made with Create workflow on the step already does.Output data: the Step ticket, Lifecycle ticket, Person, Anchor date, Step due, the person in each of the template’s roles, their Personal email, their HR record, and answers from earlier Form steps the workflow can read.Common use cases:
  • Order a laptop or create accounts when an onboarding step opens
  • Use a new hire’s form answers in a request to another system
Learn more about lifecycles and workflows
Fires when every step in a lifecycle is done or skipped.Output data: the Lifecycle ticket, Lifecycle ID, Person and Template ID.Common use cases:
  • Post a summary when onboarding finishes
  • Close the lifecycle’s parent ticket
Fires when an HR sync finds a new hire or a moved start date. Find it under the People group in the trigger picker.Output data: the Person and the Date (the start date).Common use cases:
  • Start an onboarding lifecycle with the Start Lifecycle action
Fires when an HR sync finds an employee’s last day, or a moved last day. Find it under the People group in the trigger picker.Output data: the Person and the Date (the last day).Common use cases:
  • Start an offboarding lifecycle with the Start Lifecycle action

Message triggers

Fires when a message is added to a ticket.Configuration:
  • Message Authors (optional): Limit the trigger to messages from specific users or groups.
  • Visibility (optional): Restrict the trigger to Public or Private messages. 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.
Output data:
  • ticketId - The ticket the message was added to
  • ticketMessageId - The message that was added
Common use cases:
  • 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.
Fires when an asset is created by hand, from a CSV import, or through Ravenna Assistant.Output data:
  • assetId - The ID of the asset that was created
  • actorId (Actor) - The user who made the change
Common use cases:
  • Open a setup ticket for new hardware
Fires when an asset’s name, description, type, or status is edited, or when an archived asset is unarchived. Assignment changes fire Asset Assignment Changed instead.Output data:
  • assetId - The ID of the asset that was updated
  • actorId (Actor) - The user who made the change
Common use cases:
  • Open a repair ticket when an asset moves to an Unavailable status
  • Sync status changes to an external inventory system
Fires when an asset is archived.Output data:
  • assetId - The ID of the asset that was archived
  • actorId (Actor) - The user who made the change
Common use cases:
  • Record disposal of retired hardware in an external system
Fires when someone is assigned to or unassigned from an asset, whether the change is made in Ravenna or by Ravenna Assistant. Each run covers one person on one asset: assigning two people starts two runs, and replacing one assignee with another starts one run for the person added and one for the person removed.Output data:
  • assetId - The asset whose assignees changed
  • actorId (Actor) - The user who made the change
  • Assignees - added holds the user who was assigned and removed holds the user who was unassigned. Each run fills one of the two.
  • currentAssigneeIds - Everyone who holds the asset after the change
Common use cases:
  • 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
Changes made by a workflow’s asset actions do not fire asset triggers, so an asset action cannot set off another asset workflow.

Scheduled triggers

Runs a workflow on a recurring schedule defined by a standard cron expression. Find it under the Timer group in the trigger picker.Configuration:
  • 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.
Common use cases:
  • Schedule recurring reports or cleanup tasks
  • Automate periodic ticket reviews
  • Run time-based processes
Cron-triggered workflows have no ticket context, so they cannot reference ticket fields. Use them for batch operations with Search Tickets, Search Users, or Search Assets, reports, or system maintenance.

Webhook triggers

Starts a workflow when an external system sends a request to the trigger’s Direct URL. An AI prompt turns the request body into structured fields that later steps can reference. Find it under the AI group in the trigger picker.How it works:
  1. Add the Webhook Trigger to a workflow.
  2. Copy the Direct URL and set it as the destination in the system that sends the webhook.
  3. Write a Prompt that describes how to turn the incoming payload into the fields you need.
  4. 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.
Configuration:
  • 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, or 204. Some webhook providers retry or disable the endpoint when they get an unexpected status, so pick the code their documentation specifies.
What the URL accepts:
  • Only published workflows run. A request to a draft or turned-off workflow is rejected.
  • POST requests start a run, and the response body contains the run ID. Other requests, such as health checks, get a 200 without 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 challenge parameter.
Authentication:The Direct URL carries a signed token in its 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.
Outbound calls later in the workflow, such as an HTTP Request action, support API Key, Bearer Token, and Basic Auth using vault-stored credentials.Common use cases:
  • 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 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.
Fires when the Ravenna agent sends its first reply in a Slack conversation.Output data:
  • Slack workspace, Slack channel, and Slack thread of the conversation
  • userId - The Slack user who started the conversation
  • ticketId (Tracking ticket) - The ticket tracking the conversation
Common use cases:
  • Follow up on agent conversations with an AI Conversation Monitor step
  • Log or tag tickets the agent picked up
Fires when someone gives a thumbs up or thumbs down on an agent reply in Slack.Configuration:
  • Feedback type - Negative (default) or Positive.
Output data:
  • Slack workspace, Slack channel, and Slack thread where the feedback was given
  • Feedback received - positive or negative
Common use cases:
  • Escalate a conversation to a person after negative feedback
  • Track positive feedback for reporting
Other integrations provide workflow actions, not triggers. To start a workflow from an event in another system, use the Webhook Trigger.
Learn more about every action and choosing a trigger
Last modified on November 18, 2026