Skip to main content
Automate business processes by connecting triggers that listen for events with actions that perform tasks. Every workflow needs exactly one trigger and one or more actions to create powerful automation across your integrated systems.

​
What triggers and actions can do

React to ticket events

Trigger workflows when tickets are created, assigned, or change status

Respond to Slack activity

Start automation based on emoji reactions or channel membership changes

Manage user access

Automate Okta and Google Workspace user provisioning and access control

Create external issues

Generate tickets in Linear or other systems from Ravenna events

Control workflow logic

Branch execution with conditional logic and decision trees

Integrate with APIs

Connect to any external service using HTTP requests

​
Triggers

Every workflow needs exactly one trigger that listens for specific conditions and provides context to the rest of the workflow.

​
Ravenna Triggers

​
Ticket Triggers

Responds when new tickets are created in your workspace. Filter these triggers by channel, form, or priority to automatically assign tickets, set initial tags, or notify team members.Common use cases:
  • Auto-assign tickets based on form
  • Set initial tags for categorization
  • Send welcome messages to requesters
  • Notify team members of new tickets
  • Route tickets to specialized teams
Triggers when forms are submitted or when form data is updated on tickets. Filter by specific forms to run workflows only for particular form types, enabling targeted automation based on structured request information.Trigger behavior:
  • Fires when a ticket is created with form data
  • Fires when form field values are updated on existing tickets
  • Can filter to specific forms by form selection
Common use cases:
  • Route tickets based on submitted form type
  • Auto-assign tickets from specific request forms
  • Trigger approval workflows for access request forms
  • Send notifications when critical forms are submitted
  • Apply specific tags based on form type
  • Integrate form submissions with external systems
Triggers when tickets are archived in your workspace. Use this to clean up related resources, send final notifications, or update external systems when tickets are removed from active channels.Common use cases:
  • Clean up related Slack channels
  • Send final status notifications
  • Update external tracking systems
  • Archive related documentation
Activates when tickets are assigned to users. Use this to notify assignees, update workload tracking, or trigger onboarding workflows for new ticket owners.Common use cases:
  • Notify assignees of new assignments
  • Update workload tracking systems
  • Send assignment confirmation messages
  • Trigger assignee-specific workflows
Activates when tickets move between statuses. Configure these triggers to watch for specific status transitions and filter by channel or assignee. Use these to send notifications, update related systems, or trigger follow-up processes.Common use cases:
  • Send notifications on status changes
  • Update external systems when tickets are resolved
  • Trigger follow-up workflows based on status
  • Track ticket lifecycle metrics
Triggers when tags are added to or removed from tickets. The trigger provides information about which tags were added and which were removed, allowing you to respond differently based on the type of change.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
  • Trigger workflows based on tag combinations
  • Track tag-based ticket categorization
  • Auto-assign tickets based on tag changes
Triggers when tickets are approved or declined through approval workflows. Use this to continue multi-step processes, notify stakeholders, or take action based on approval decisions.Common use cases:
  • Continue workflows after approval
  • Notify stakeholders of decisions
  • Provision access after approval
  • Handle declined requests appropriately

​
Task Triggers

Triggers when individual tasks within a task template are marked as completed. Workflows can take action the moment a task is finished, including pinging the owner of the next task to create seamless handoffs. Automations have access to both the current completed task and the next task in the sequence.Output data:
  • ticketId - The ID of the ticket containing the task
  • taskItemId - The ID of the completed task item
  • currentTask - Information about the task that was just completed
  • nextTask - Information about the next task in the sequence (if any)
  • currentTaskAssigneeIds - User IDs of assignees on the completed task
  • nextTaskAssigneeIds - User IDs of assignees on the next task
  • hasMoreTasks - Boolean indicating if there are more tasks remaining
Common use cases:
  • Notify next task assignees when their task becomes active
  • Send completion notifications to stakeholders
  • Update external systems when process steps finish
  • Trigger approval workflows for completed tasks
  • Create seamless task handoffs between team members
  • Escalate if tasks are completed outside SLA windows

​
Message Triggers

Triggers when messages are added to tickets. Use this to analyze message content, notify team members, or trigger automated responses based on message patterns.Common use cases:
  • Analyze message sentiment
  • Notify team members of updates
  • Trigger automated responses
  • Track conversation patterns

​
Agent Triggers

Allows AI Agents to trigger workflows through natural language rules. When you reference a workflow using @Workflow Name in an agent rule, the agent can execute that workflow based on user requests or specific scenarios.How it works:
  1. Create a workflow with an Agent Trigger
  2. Optionally configure a form to collect required information
  3. Reference the workflow in your agent’s rules using @Workflow Name
  4. The agent will trigger the workflow when conditions in the rule are met
Configuration:
  • Form (optional): Select a form to collect structured information before the workflow runs. If configured, users will see a pre-filled form to review and submit. Without a form, the workflow executes immediately.
  • Agents: Select which agents have access to trigger this workflow
Common use cases:
  • Automate employee onboarding processes triggered by agent conversations
  • Provision software access based on agent-identified needs
  • Create approval workflows for requests classified by agents
  • Trigger multi-step processes without manual intervention
  • Execute complex automations based on conversational context
Example rule:
When a user requests software access, ask which application they need and 
their business justification. Then trigger @Workflow - Software Access Request 
with the details provided.
Agents must have explicit access to workflows. Reference workflows in rules using @ mentions to grant access.

​
Scheduled Triggers

Runs workflows on a cron schedule. Use this to trigger recurring workflows, schedule periodic tasks, or automate time-based processes.Common use cases:
  • Schedule recurring workflows
  • Automate periodic tasks
  • Run time-based processes
  • Trigger scheduled reports

​
Slack Triggers

​
Reaction Triggers

Responds when users add specific emoji reactions to messages. Filter by emoji type, channel, or user to escalate tickets or create tickets from flagged messages.Common use cases:
  • Create tickets from flagged messages
  • Escalate issues based on reaction types
  • Track team sentiment on messages
  • Trigger workflows from emoji-based voting
Triggers when users remove emoji reactions from messages. Use this to undo actions, track reaction changes, or update workflows based on removed reactions.Common use cases:
  • Undo actions when reactions removed
  • Track reaction changes
  • Update workflow state
  • Monitor sentiment changes

​
Member Triggers

Activates when users join Slack channels. Use this to send welcome messages, assign onboarding tasks, or notify team members of new channel members.Common use cases:
  • Send welcome messages
  • Assign onboarding tasks
  • Notify team of new members
  • Trigger channel-specific workflows
Triggers when users leave Slack channels. Use this to clean up permissions, notify team members, or update access controls.Common use cases:
  • Clean up channel permissions
  • Notify team of departures
  • Update access controls
  • Track channel membership changes
Activates when new users join your Slack workspace. Use this to trigger onboarding workflows, provision initial access, or send welcome messages to new team members.Common use cases:
  • Trigger onboarding workflows
  • Provision initial access
  • Send welcome messages
  • Create onboarding tickets

​
Actions

Actions perform work in your workflows. Actions use information from triggers and previous actions to make dynamic decisions and process data.

​
Ticket Actions

Generates new tickets with configurable properties like title, description, channel assignment, priority, and tags. Use information from triggers to populate ticket details or create follow-up tickets that reference original ticket information.Common use cases:
  • Create follow-up tickets for multi-step processes
  • Generate tickets from Slack messages
  • Auto-create tickets based on external events
  • Split complex requests into multiple tickets
Modifies existing tickets by changing properties like priority, tags, or custom fields. Use these to escalate tickets, add processing tags, or update fields based on workflow progress.Common use cases:
  • Escalate tickets by changing priority
  • Add processing or status tags
  • Update custom fields based on workflow logic
  • Modify ticket properties dynamically
Changes ticket status and can include resolution notes or assignee notifications. Use these to resolve certain types of tickets or move tickets through your support process based on completion criteria.Common use cases:
  • Auto-resolve tickets meeting specific criteria
  • Move tickets through workflow stages
  • Add resolution notes automatically
  • Notify assignees of status changes
Updates the priority level for tickets based on workflow conditions. Use this to escalate urgent issues, adjust priorities based on SLA requirements, or dynamically prioritize based on ticket content.Common use cases:
  • Escalate urgent issues automatically
  • Adjust priorities based on SLA
  • Prioritize based on ticket content
  • Update priority after analysis
Assigns tickets to specific users or teams. Configure assignment logic based on ticket properties, user availability, or workload balancing rules.Common use cases:
  • Round-robin ticket assignment
  • Assign based on expertise or tags
  • Balance workload across team members
  • Route tickets to specific teams
Adds followers to tickets to keep stakeholders informed. Use this to automatically include relevant team members, managers, or cross-functional partners in ticket updates.Common use cases:
  • Add managers to high-priority tickets
  • Include cross-functional stakeholders
  • Keep team members informed
  • Notify relevant parties automatically
Adds approvers to tickets requiring approval workflows. Select approvers from Ravenna members or groups, including groups synced from third-party integrations.Assignment strategy:
  • All: Assigns everyone in the selected list as approvers. Any one of them can approve the request.
  • Round Robin: Assigns one approver from the list using rotation to balance workload across the team.
Common use cases:
  • Route approvals to managers with load balancing via Round Robin
  • Add all qualified approvers and let the first available person approve
  • Assign approvers by department using Round Robin for fair distribution
  • Reference access level assignment strategies for application access requests
Pauses workflow execution until a ticket receives approval or is declined. Use this to gate access provisioning, resource allocation, or other actions that require authorization.Behavior with assignment strategies:
  • Auto: Workflow continues immediately without waiting (auto-approved by system bot)
  • All: Waits for any one of the assigned approvers to respond
  • Round Robin: Waits for the single assigned approver to respond
  • Honors the assignment strategy set by preceding “Add Approvers” actions
Common use cases:
  • Gate access provisioning until an approver responds
  • Wait for manager approval before proceeding
  • Pause before resource allocation until authorized
  • Reference access level assignment strategies for application requests
Adds tags to tickets for categorization and filtering. Use this to automatically tag tickets based on content analysis, form, or workflow conditions.Common use cases:
  • Auto-tag based on content
  • Categorize by form
  • Add processing status tags
  • Tag for reporting purposes
Relocates tickets between different workspaces, channels, or statuses within your organization. Use to transfer tickets between teams, escalate issues to different departments, or reorganize tickets based on changing requirements. The action supports cross-workspace moves while maintaining ticket history and context.Common use cases:
  • Transfer tickets between teams
  • Escalate to different departments
  • Move tickets across workspaces
  • Reorganize tickets based on criteria
Sends customer satisfaction surveys to users after ticket resolution. Use this to gather feedback, measure service quality, and identify areas for improvement.Common use cases:
  • Survey after ticket resolution
  • Measure service quality
  • Gather user feedback
  • Track satisfaction metrics
Monitors tickets until specific conditions are met, then continues workflow execution. Use this to wait for status changes, message updates, or other ticket events before proceeding.Common use cases:
  • Wait for status changes
  • Monitor for specific updates
  • Track ticket progress
  • Trigger actions on conditions
Pauses workflow execution until a ticket has been inactive for a specified duration. Use this to automatically take action when requests go quiet, helping teams stay responsive by resolving or closing tickets when people stop responding. This keeps channels clean and SLAs on track.Common use cases:
  • Auto-resolve tickets after inactivity period
  • Close stale tickets automatically
  • Send reminder messages before auto-closing
  • Escalate tickets with no response
Sends new messages on tickets to communicate with requesters or team members. Use this to provide updates, request information, or share automated responses.Common use cases:
  • Send automated updates
  • Request additional information
  • Share status notifications
  • Provide automated responses
Checks if there are any new messages on a ticket since the last check. Use this in monitoring workflows to detect when users respond or team members add updates.Common use cases:
  • Detect user responses
  • Monitor for team updates
  • Track conversation activity
  • Trigger actions on new messages

​
Slack Actions

Delivers private messages to specific users. Use these to notify assignees about new tickets, alert managers about escalations, or provide status updates to requesters. Messages can include dynamic information from earlier workflow steps.Common use cases:
  • Notify assignees of new tickets
  • Alert managers about escalations
  • Send status updates to requesters
  • Deliver personalized notifications
Posts to Slack channels with optional mentions and formatting. Use these to announce high-priority tickets, share status updates, or coordinate team responses.Common use cases:
  • Announce high-priority tickets
  • Share status updates with teams
  • Coordinate team responses
  • Broadcast important notifications
Creates a new Slack thread specifically for a Ravenna ticket. Use this to establish dedicated communication channels for ticket discussions while keeping conversations organized.Common use cases:
  • Create dedicated ticket threads
  • Organize ticket discussions
  • Enable threaded collaboration
  • Keep ticket conversations separate
Creates new Slack channels with configurable properties like name, description, and privacy settings. Use this to establish dedicated channels for incidents, projects, or team coordination.Common use cases:
  • Create incident channels
  • Establish project channels
  • Set up team coordination spaces
  • Automate channel creation
Updates existing Slack channel properties including name, topic, description, and settings. Use this to maintain channel information, update purposes, or modify channel configurations.Common use cases:
  • Update channel topics
  • Modify channel descriptions
  • Change channel settings
  • Maintain channel information
Archives Slack channels to clean up workspace and preserve channel history. Use this to automatically archive channels after incidents are resolved or projects are completed.Common use cases:
  • Archive incident channels
  • Clean up completed projects
  • Preserve channel history
  • Maintain workspace organization
Sends a message in Slack requesting users to fill out form forms. Use this to gather additional information, complete intake processes, or collect required details for ticket processing.Common use cases:
  • Request additional information
  • Complete intake processes
  • Gather required details
  • Collect form responses

​
Okta Actions

Creates a new user in Okta with email, first name, and last name. The user is automatically activated upon creation. Use this to automate user provisioning during onboarding workflows.Input fields:
  • Email - Email address for the user (used as login email)
  • First Name - User’s first name
  • Last Name - User’s last name
Common use cases:
  • Automate new employee account creation during onboarding
  • Provision Okta accounts from HR system triggers
  • Create user accounts as part of access request workflows
  • Set up contractor accounts with automated workflows
Permanently removes one or more users from Okta. Use this for offboarding workflows or to clean up accounts that are no longer needed.Input fields:
  • User IDs - One or more Ravenna user IDs to remove (supports user groups)
Common use cases:
  • Automate account removal during employee offboarding
  • Clean up unused or orphaned accounts
  • Remove contractor accounts after engagement ends
  • Implement automated account lifecycle policies
Activates one or more deactivated users in Okta, restoring their access to applications and groups. Use this when employees return from leave or when accounts need to be reactivated.Input fields:
  • User IDs - One or more Ravenna user IDs to activate (supports user groups)
Common use cases:
  • Reactivate accounts when employees return from leave
  • Restore access after security review clears an account
  • Re-enable contractor accounts for new engagements
  • Implement automated account reactivation workflows
Deactivates one or more users in Okta, suspending their access to all applications and groups without permanently deleting the account. Use this for temporary access suspension or as part of offboarding workflows.Input fields:
  • User IDs - One or more Ravenna user IDs to deactivate (supports user groups)
Common use cases:
  • Suspend access during employee offboarding
  • Temporarily disable accounts for employees on extended leave
  • Respond to security incidents by quickly disabling compromised accounts
  • Implement automated account suspension policies
Looks up a user in Okta by their email address and returns whether the user exists along with their Ravenna user ID if found. Use this to verify user existence before performing other actions or to find users dynamically in workflows.Input fields:
  • Email - Email address to search for in Okta
Output data:
  • isSuccess - Boolean indicating if the user was found in Okta
  • userId - The Ravenna user ID if the user was found
Common use cases:
  • Verify user exists before provisioning access
  • Look up users dynamically in conditional workflows
  • Check if accounts already exist before creating new ones
  • Find users by email for downstream workflow actions
Adds one or more users to an Okta group. Use this to grant team access, provision group-based permissions, or automate group membership during onboarding.Common use cases:
  • Automate onboarding group assignments
  • Grant team access automatically
  • Provision group-based permissions
  • Add users to distribution lists
Removes one or more users from an Okta group. Use this to revoke access, handle offboarding, or update group memberships based on role changes.Common use cases:
  • Revoke access during offboarding
  • Update group memberships
  • Remove temporary access
  • Handle role changes
Assigns one or more users to an Okta application. Use this to provision application access, automate software assignments, or grant tool access based on request approvals.Common use cases:
  • Provision application access
  • Automate software assignments
  • Grant tool access after approval
  • Assign applications during onboarding
Removes one or more users from an Okta application. Use this to revoke application access, handle offboarding, or remove unused software assignments.Common use cases:
  • Revoke application access
  • Handle application offboarding
  • Remove unused assignments
  • Update application access
Resets MFA authenticators and/or passwords for users in Okta. Choose to reset MFA only, password only, or both simultaneously. This consolidated action provides flexible security management for various scenarios.Scope options:
  • MFA Only: Resets all MFA authenticators, requiring re-enrollment
  • Password Only: Sends forgot password email to user
  • Both: Resets both MFA and password simultaneously
Common use cases:
  • Help users with lost MFA devices
  • Handle security incidents requiring full credential reset
  • Reset compromised authentication methods
  • Automate password reset requests
  • Troubleshoot MFA issues
  • Handle locked account scenarios
Generates a password reset token for users in Okta. Use this to provide direct reset links, integrate with custom workflows, or handle password resets programmatically.Common use cases:
  • Provide direct reset links
  • Integrate with custom workflows
  • Handle programmatic resets
  • Generate temporary access tokens
Sets a specific password for users in Okta. Use this for initial account setup, temporary password provisioning, or automated password management workflows.Common use cases:
  • Set initial account passwords
  • Provision temporary passwords
  • Automate password management
  • Handle emergency access
Checks if a user is a member of a specific Okta group. Use this to validate access, make conditional workflow decisions, or verify group memberships before granting permissions.Common use cases:
  • Validate access before actions
  • Make conditional decisions
  • Verify group memberships
  • Check permission prerequisites

​
Google Workspace Actions

Creates a new Google Group with specified name, description, and optional email address. Use this to programmatically provision groups for teams, projects, or access management.Common use cases:
  • Create project-specific groups automatically
  • Provision team groups during onboarding
  • Set up distribution lists programmatically
  • Create groups for access management
Creates a new user in Google Workspace with specified name, email, and optional secondary email. Generates a secure initial password that the user must change on first login. The primary email is constructed from the provided username and the domain configured in your Google Workspace integration.Input fields:
  • Username - Will be combined with workspace domain to form the users primary email
  • First Name - User’s first name
  • Last Name - User’s last name
  • Secondary Email (optional) - Additional email address for the user
Common use cases:
  • Automate new employee account creation during onboarding
  • Provision Google Workspace accounts from HR system triggers
  • Create service accounts programmatically
  • Set up contractor accounts with automated workflows
Checks if an email address is available in Google Workspace before creating users or aliases. Returns a boolean result that enables conditional branching in workflows to handle email conflicts gracefully.Input fields:
  • Workspace ID - The workspace to check in
  • Email - Email address to check (accepts username only or full email address)
Output data:
  • isSuccess - Boolean indicating if the email is available (true = available, false = unavailable)
  • reason - Explanation if email is unavailable (e.g., “Email is already in use as a primary email” or “Email is already in use as an alias”)
Conditional branching: This action returns a boolean isSuccess field, which automatically enables if/else workflow branches:
  • If available (success): Proceed to create user or alias
  • If unavailable (failed): Handle conflict, notify user, or try alternative email
Common use cases:
  • Verify email availability before creating Google Workspace users
  • Check if email alias is available before assigning it
  • Implement email conflict handling with conditional logic
  • Validate requested email addresses in onboarding workflows
  • Try multiple email variations until finding an available one
Creates an email alias for a user in Google Workspace. Email aliases allow users to receive mail at additional addresses that deliver to their primary inbox. Use the Check Email Availability action before creating aliases to implement conditional logic that handles email conflicts gracefully.Input fields:
  • User - The Ravenna user to create an alias for
  • Email Alias - The email alias to create. Accepts either a static email address in your domain or a dynamic reference to use values from previous workflow steps.
Output data:
  • isSuccess - Boolean indicating if the alias was created successfully
  • User Email - The user’s primary email address
  • Email Alias - The email alias that was created
Common use cases:
  • Create department-based aliases (e.g., support@, sales@) for individuals
  • Set up role-based aliases during job changes or promotions
  • Create project-specific aliases for team members
  • Add branded aliases for customer-facing employees
  • Dynamically create aliases using email values from form submissions or previous workflow steps
Retrieves detailed information and settings for a Google Group including membership policies, posting permissions, moderation settings, and discovery options. Use this to audit group configurations, verify settings before modifications, or gather group details for reporting.Output data:
  • Group ID, email, name, and description
  • Membership settings (who can join, view membership, leave)
  • Posting settings (who can post, reply-to configuration)
  • Moderation settings (message and spam moderation levels)
  • Discovery and visibility settings
  • Collaborative inbox configuration
Common use cases:
  • Audit group settings for compliance
  • Verify group configuration before changes
  • Gather group information for reporting
  • Check group permissions in conditional workflows
Updates settings and configuration for an existing Google Group. Modify membership policies, posting permissions, moderation levels, and other group settings programmatically.Configurable settings:
  • Basic info (name, description)
  • Membership settings (who can join, view membership, leave, contact owner)
  • Posting settings (who can post, allow web posting, reply-to)
  • Moderation settings (message and spam moderation levels)
  • Discovery and visibility settings
  • Collaborative inbox configuration
Common use cases:
  • Enforce group settings policies automatically
  • Update group configurations during lifecycle events
  • Modify permissions based on workflow conditions
  • Standardize group settings across organization
Deletes a Google Group from Google Workspace. Use this to clean up unused groups, remove temporary project groups, or manage group lifecycle as part of offboarding or project completion workflows.Common use cases:
  • Remove temporary project groups after completion
  • Clean up unused distribution lists
  • Delete groups during team offboarding
  • Manage group lifecycle automatically
Lists all Google Groups with their details including email address, name, and description. Returns both a simple array of group IDs for downstream actions and detailed group information for display.Output data:
  • isSuccess - Boolean indicating if the operation succeeded
  • groupIds - Array of Google Group IDs (strings) for use in downstream workflow actions like Add Users to Group or Remove Users from Group
  • groups - Array of group objects with detailed information, each containing:
    • Group Email - The group’s email address
    • Name - The group name
    • Description - The group description
Common use cases:
  • Iterate over all groups to perform bulk operations
  • Build dynamic group selection dropdowns
  • Audit existing group configurations
  • Generate group inventory reports
  • Populate group management interfaces
  • Pass group IDs to downstream workflow actions
Adds one or more users to a Google Group. Use this to grant team access, provision group-based permissions, or automate group membership during onboarding.Common use cases:
  • Automate onboarding group assignments
  • Grant team access automatically
  • Provision group-based permissions
  • Add users to distribution lists
Removes one or more users from a Google Group. Use this to revoke access, handle offboarding, or update group memberships based on role changes.Common use cases:
  • Revoke access during offboarding
  • Update group memberships
  • Remove temporary access
  • Handle role changes
Checks if a user is a member of a specific Google Group. Use this to validate access, make conditional workflow decisions, or verify group memberships before granting permissions.Common use cases:
  • Validate access before actions
  • Make conditional decisions
  • Verify group memberships
  • Check permission prerequisites
Resets MFA authenticators and/or passwords for users in Google Workspace. Choose to reset MFA only, password only, or both simultaneously for comprehensive security management.Scope options:
  • MFA Only: Turns off 2-Step Verification, requiring re-enrollment
  • Password Only: Forces password change at next login
  • Both: Resets both MFA and password simultaneously
Common use cases:
  • Help users with lost MFA devices
  • Handle security incidents requiring credential reset
  • Force password changes for compromised accounts
  • Reset authentication for locked accounts
  • Troubleshoot MFA issues
Suspends one or more users in Google Workspace. Suspended users cannot sign in to their accounts or access any Google services. Use this for offboarding workflows, security incident response, or temporary account deactivation.Input fields:
  • User IDs - One or more Ravenna user IDs to suspend (supports user groups)
Output data:
  • isSuccess - Boolean indicating if the users were suspended successfully
Common use cases:
  • Automate account suspension during employee offboarding
  • Respond to security incidents by quickly disabling compromised accounts
  • Temporarily deactivate accounts for employees on extended leave
  • Implement automated account lifecycle policies
Restores (unsuspends) one or more previously suspended users in Google Workspace. Restored users regain access to their accounts and all Google services. Use this when employees return from leave or when accounts need to be reactivated.Input fields:
  • User IDs - One or more Ravenna user IDs to restore (supports user groups)
Output data:
  • isSuccess - Boolean indicating if the users were restored successfully
Common use cases:
  • Reactivate accounts when employees return from leave
  • Restore access after security review clears an account
  • Re-enable contractor accounts for new engagements
  • Implement automated account reactivation workflows

​
Incident.io Actions

Validates if a user is a member of an on-call group in Incident.io. Use this to verify on-call status, route incidents to appropriate responders, or make conditional decisions based on on-call schedules.Common use cases:
  • Verify on-call status
  • Route incidents to responders
  • Check escalation eligibility
  • Validate incident assignments

​
PagerDuty Actions

Validates if a user is currently on-call for a specific PagerDuty schedule. Use this to verify on-call status before escalating tickets, route incidents to the right responders, or make conditional decisions based on on-call schedules.Common use cases:
  • Verify on-call status before escalation
  • Route incidents to on-call responders
  • Check escalation eligibility
  • Validate incident assignments based on schedules

​
Control Flow Actions

Pauses workflow execution for specified durations. Use these to create delays between actions or allow time for external processes to complete.Common use cases:
  • Add delays between actions
  • Wait for external processes
  • Create timed follow-ups
  • Implement timeout logic
Evaluates conditional expressions to make workflow decisions. Use this to branch workflow logic, filter actions based on conditions, or implement complex decision trees.Common use cases:
  • Branch workflow logic
  • Filter actions by conditions
  • Implement decision trees
  • Create conditional paths
Provides conditional branching with if/else logic. Use this to execute different actions based on conditions, handle multiple scenarios, or create alternative workflow paths.Common use cases:
  • Execute different actions
  • Handle multiple scenarios
  • Create alternative paths
  • Implement conditional logic
Jumps to a specific node in the workflow. Use this to create loops, skip steps, or implement complex workflow navigation patterns.Common use cases:
  • Create workflow loops
  • Skip workflow steps
  • Implement navigation patterns
  • Jump to specific nodes

​
AI Actions

Transforms complex ticket histories into clear, actionable summaries. AI distills essential information from lengthy conversation threads and status changes into concise summaries that capture what happened, what was decided, and what outcomes were achieved.Common use cases:
  • Generate ticket summaries for handoffs
  • Create executive briefings
  • Summarize resolution steps
  • Extract key decisions from conversations
Evaluates complex conditions that require contextual evaluation beyond simple rule-based logic. The workflow continues down one of two paths based on the AI’s decision.Common use cases:
  • Route tickets based on content analysis
  • Make priority decisions contextually
  • Evaluate sentiment for escalation
  • Determine appropriate next actions
Embeds AI reasoning directly into workflows to analyze context, generate responses, or make dynamic decisions. Use this to summarize information, draft messages, determine next steps, or process unstructured data based on custom instructions you provide.Common use cases:
  • Summarize ticket context for handoffs
  • Draft response messages based on ticket content
  • Generate dynamic next steps from conversation history
  • Analyze sentiment or urgency from messages
  • Extract structured data from unstructured text
  • Create custom summaries for specific audiences

​
Fleet Device Management Actions

Retrieves all hosts associated with a user from Fleet, returning basic host information for each device. Use this to identify user devices before performing other Fleet operations.Common use cases:
  • List all devices assigned to a user
  • Verify device ownership before granting access
  • Identify which device to target for Fleet operations
  • Gather device inventory for a user
Checks comprehensive device health metrics including battery status, disk encryption, MDM enrollment, OS updates, and uptime. Use this to ensure devices meet security and compliance requirements.Common use cases:
  • Verify security compliance before access approval
  • Check device health for troubleshooting
  • Ensure disk encryption is enabled
  • Validate MDM enrollment status
Lists all software installed on a user’s device with version information and vulnerability details. Optionally filter to show only software with known vulnerabilities for security auditing.Common use cases:
  • Audit installed software for compliance
  • Identify vulnerable applications
  • Track software inventory
  • Security risk assessment
Executes custom osquery SQL statements or predefined diagnostic queries on user devices to gather specific system information. Use this for advanced troubleshooting and system analysis.Predefined query types:
  • System information
  • OS version details
  • Logged in users
  • Running processes
  • Network interfaces
  • Disk space usage
  • Recent items
Common use cases:
  • Advanced device troubleshooting
  • Custom system information gathering
  • Security investigation queries
  • Performance diagnostics
Locks devices remotely through Fleet MDM to secure lost, stolen, or compromised devices. Returns an unlock PIN for each locked device that can be shared with the user.Input fields:
  • hosts - Array of hosts to lock (from Get User Hosts action)
Output data:
  • hosts - Array of locked hosts with their unlock PINs
Common use cases:
  • Lock lost or stolen devices immediately
  • Secure compromised devices during security incidents
  • Enforce device security policies for non-compliant devices
  • Remotely secure devices during employee offboarding
Retrieves the disk encryption key for hosts that have escrowed their encryption keys with Fleet. Use this to help users recover access to encrypted devices.Input fields:
  • hosts - Array of hosts to retrieve encryption keys for (from Get User Hosts action)
Output data:
  • hosts - Array of hosts with their encryption keys and the timestamp when the key was last updated
Common use cases:
  • Help users recover access to encrypted devices
  • Retrieve escrowed encryption keys for device recovery
  • Support disk recovery scenarios when users forget their password

​
Jamf Device Management Actions

Retrieves all computers associated with a user from Jamf Pro, returning basic device information for each computer. Use this to identify user devices before performing other Jamf operations.Common use cases:
  • List all computers assigned to a user
  • Verify device ownership before granting access
  • Identify which computer to target for Jamf operations
  • Gather device inventory for a user
Locks Apple devices remotely through Jamf Pro MDM to secure lost, stolen, or compromised devices. Generates a 6-digit unlock PIN for each locked device that can be shared with the user.Input fields:
  • computers - Array of computers to lock (from Get User Computers action)
Output data:
  • computers - Array of locked computers with their unlock PINs
Common use cases:
  • Lock lost or stolen Mac devices immediately
  • Secure compromised devices during security incidents
  • Enforce device security policies for non-compliant devices
  • Remotely secure devices during employee offboarding
Retrieves the FileVault recovery key for Mac computers that have escrowed their encryption keys with Jamf Pro. Use this to help users recover access to encrypted Mac devices.Input fields:
  • computers - Array of computers to retrieve FileVault keys for (from Get User Computers action)
Output data:
  • computers - Array of computers with:
    • FileVault recovery key
    • Boot partition encryption details (partition name, FileVault state, encryption percentage)
    • Recovery key validity status
    • Institutional recovery key presence
    • Disk encryption configuration name
Common use cases:
  • Help users recover access to encrypted Mac devices
  • Retrieve escrowed FileVault keys for device recovery
  • Verify FileVault encryption status on devices
  • Support disk recovery scenarios when users forget their password

​
Linear Actions

Creates new issues in Linear with configurable properties like title, description, project assignment, priority, and labels. Use information from triggers and other actions to populate issue details or create issues based on Ravenna ticket events.Common use cases:
  • Create Linear issues from Ravenna tickets
  • Mirror ticket updates to Linear workspace
  • Track development work from support requests
  • Sync incident reports to Linear projects

​
Tools Actions

Calls external APIs to integrate with third-party services. Use this to send data to external systems, fetch information from APIs, or trigger actions in other platforms.Common use cases:
  • Integrate with third-party services
  • Send data to external systems
  • Fetch information from APIs
  • Trigger actions in other platforms

​
Configuring Triggers and Actions

Use filters to ensure workflows only execute for relevant events. Test your trigger conditions with realistic data to verify they work as expected. Action configuration involves mapping data from triggers and previous actions to action inputs. The workflow builder provides tools to reference information from earlier steps. Data flows automatically between workflow steps. Information captured by triggers becomes available to actions.

​
Best Practices

Create triggers with precise conditions to avoid unnecessary executions. Use filters for channel, priority, status, or user criteria. Monitor trigger frequency to identify issues with overly broad conditions.
Configure actions to be idempotent when possible so they can be safely repeated without causing problems. This makes workflows more reliable when they need to retry after failures.
Test workflows with realistic data that represents actual conditions. Pay attention to edge cases and error conditions to ensure workflows handle unexpected situations gracefully.
Give triggers and actions clear names that explain what they do. This makes workflows easier to understand and maintain, especially when multiple team members work with them.
Add descriptions explaining non-obvious logic or business rules. This helps team members understand why workflows behave in certain ways.