> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ravenna.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Triggers

> Reference for every Ravenna workflow trigger: ticket, task, lifecycle, message, asset, schedule, webhook, and Slack events, with their filters and outputs.

Every workflow starts from exactly one trigger. The trigger listens for an event, and its data is available to every step after it.

## Trigger reference

| Trigger | Picker group | When it fires | Key outputs |
| - | - | - | - |
| Ticket Created | Ticket | A ticket is created (optionally from chosen forms) | Ticket |
| Form Submitted | Ticket | A chosen form is submitted or its values change on a ticket | Ticket and the form's fields |
| Category Assigned | Ticket | A chosen category is set or changed, including at creation | Ticket |
| Ticket Archived | Ticket | A ticket is archived | Ticket |
| Ticket Assigned | Ticket | A ticket is assigned | Ticket |
| Ticket Status Changed | Ticket | A ticket moves into one of the chosen statuses | Ticket |
| Ticket Tags Changed | Ticket | Tags are added or removed | Ticket, added tags, removed tags |
| Ticket Approval | Ticket | A ticket is approved or declined | Ticket, Is Approved, Approved By, Declined By |
| SLA Outcome Changed | Ticket | One SLA target is attached, alerting, met, or breached | Ticket |
| Reminder Expired | Ticket | An approval, assignment, or SLA reminder fires | Ticket, reminder type |
| Entitlement Status Changed | Ticket | An entitlement enters one of the chosen statuses | Ticket, entitlement |
| Task Item Completed | Ticket | Any task on a ticket is completed (filter by template, task, name, assignees) | Ticket, task, task name, completed by, completed at |
| Task Template Applied | Ticket | A task template is applied | Ticket, task template |
| Lifecycle Step | Ticket | A lifecycle's Workflow step opens | Step ticket, lifecycle ticket, person, dates, roles |
| Lifecycle Completed | Ticket | Every lifecycle step is done or skipped | Lifecycle ticket, person |
| Employee Hired / Employee Leaving | People | HR sync reports a start date or last day | Person, date |
| Message Sent | Message | A message is added (filter by author and visibility) | Ticket, message |
| Asset Created / Updated / Archived / Assignment Changed | Asset | An asset changes | Asset, actor; assignment adds added/removed user and current assignees |
| Cron | Timer | A cron schedule fires (timezone defaults to UTC) | None |
| Webhook Trigger | AI | A POST reaches the Direct URL of a published workflow | AI Response plus fields parsed by the prompt |
| Slack Reaction Added / Removed | Slack | An emoji reaction changes in chosen channels | Slack user, channel, message, emoji, ticket |
| Slack User Joined Channel / Left Channel / Joined Team | Slack | Slack membership changes | Slack channel, user |
| AI Start Conversation Trigger | Slack | The Ravenna agent sends its first reply in a Slack conversation | Slack workspace, channel, thread, user, tracking ticket |
| AI Feedback Trigger | Slack | Thumbs up or down on an agent reply (default: negative) | Slack workspace, channel, thread, feedback type |

## Gotchas

* **Form Submitted fires on updates too.** Changing form values on an existing ticket fires it again, so design for re-runs.
* **Category Assigned fires at creation.** A ticket created with a category fires it, so Ticket Created and Category Assigned are not both needed for the same case.
* **Ticket Created vs Form Submitted.** Use Ticket Created for broad routing. Use Form Submitted when specific forms or their field values drive the workflow.
* **Task Item Completed has no "next task" output.** It reports the completed task only. Look up other tasks with later steps if needed.
* **SLA Outcome Changed fires per target.** A ticket with first response, resolution, and close targets can fire three times for the same status.
* **Cron has no ticket context.** Pair it with Search Tickets, Search Users, Search Assets, or Search Entitlements and a Loop.
* **Webhook Trigger only runs published workflows.** Drafts and turned-off workflows reject requests. The URL is a bearer secret. Verification handshakes from Okta, Slack, Microsoft Graph, Meta, and generic challenge providers are answered without running the workflow. Bodies are limited to 10 MB.
* **Trigger filters support OR.** One workflow can cover several cases without duplicating it. Filter logic: [Conditions and branching](https://docs.ravenna.ai/documentation/automate/workflows/conditions-branching.md#how-conditions-combine).
* **Asset actions do not fire asset triggers.** A workflow's own asset changes never start another asset workflow.
* **Only Slack provides integration triggers.** Other integrations offer actions only. For events from other systems, use the Webhook Trigger.
* **Microsoft Teams reactions are not workflow triggers.** Teams uses a fixed set of [emoji actions](https://docs.ravenna.ai/integrations/microsoft-teams/emoji-actions.md) that drive built-in ticket actions.


## Related topics

- [Choose triggers and actions](https://docs.ravenna.ai/documentation/automate/workflows/triggers-actions.md)
- [List agent trigger workflows](https://docs.ravenna.ai/api/workflow/list-agent-trigger-workflows.md)
- [Trigger knowledge gaps detection immediately](https://docs.ravenna.ai/api/knowledge-gaps-schedule/trigger-knowledge-gaps-detection-immediately.md)
- [Manually trigger auto-tagging for a ticket](https://docs.ravenna.ai/api/ticket/manually-trigger-auto-tagging-for-a-ticket.md)
- [Workflows](https://docs.ravenna.ai/documentation/automate/workflows/overview.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.