Overview

When creating a workflow, you start by selecting a workflow trigger.

Torii has 2 types of triggers:

1. State-based triggers

These triggers define criteria that will be evaluated against Torii the next time data is synced with external sources (integrations). If an entity meets the criteria, the workflow will trigger and run through its actions sequentially.

2. Event-based triggers

These triggers define 3d party app events which Torii continuously monitors. If an event happens in an integrated app, the workflow will trigger immediately and run through its actions sequentially.

The following event-based trigger is available:

See below for descriptions and examples for each workflow trigger.

• This is the most powerful trigger, which allows you to define a combination of criteria per user. You can tie criteria to user attributes that are Torii-specific (e.g. number of apps used by a user), or to attributes related to an application that is integrated with Torii (e.g. user status in Okta, user hire date in BambooHR, user license type in Zoom and many more). You can also combine different criteria by adding several filters, to set up a highly specific trigger for unique scenarios in your organization.
• The two scenarios where this trigger is especially useful are handling user onboarding and offboarding. You can define a unique set of criteria (e.g. active BambooHR users who belong to the Sales department and are located in Germany) and run onboarding actions when such users are first discovered (e.g. to create a Salesforce user, and users in other applications that the new employees will need).
  

2. User joins

• Use this trigger to tie your workflow to user creation or hire date in your source of truth for the user lifecycle.
  • If your source of truth is an SSO (Google Workspace, Azure AD, Okta, OneLogin, or Jumpcloud), the workflow will be triggered each time Torii discovers a new user in these IDP providers.
  • If your source of truth is an HRMS, the workflow will be triggered each time Torii discovers a new user with a future hire date.
• This trigger will help you to handle onboarding processes in your organization.
• You can define to run various actions for the newly hired employees, e.g., creating users in various applications, sending emails to new employee managers, and many more.

• Use this trigger to tie your workflow to user removal or deactivation in your source of truth for the user lifecycle.
• Triggering workflows with "User left" will help you to handle offboarding processes. For example, if your source of truth is OneLogin, you can define that when a user becomes a past user in OneLogin, you delete the user from various applications used in your organization.

Important to know - 

If your source of truth is Google, past user attributes will be updated in Torii in real-time, and workflows with "User left" trigger will be triggered within 1h after a user was suspended, archived or deleted in Google. 

For other sources of truth, past user attributes will be updated in Torii only after the app defined as a source of truth is fully synced. 

Important to know - 

If your source of truth is Google, we recommend using App event trigger to initiate user offboarding in real time and without delays.

• Similar to the "User meets criteria" trigger, the "App meets criteria" trigger allows the creation of a dynamic set of criteria in the context of applications. See below examples of scenarios in which the trigger can be especially useful:

• The trigger fires once a day per app per user.
• The trigger will only start workflows for users who use a closed app after the workflow's activation time.

• You can set up thresholds for a number of licenses per each app license type and license status. A workflow will run whenever its threshold is reached.
• Using this trigger can help you optimize your license management processes to remove wasted licenses or, on the contrary, buy licenses in advance.
  For example, you can define a workflow to trigger when Torii identifies 5 and more Zoom basic licenses that have not been used recently and remove these.
  

• This trigger allows you to set up a flexible combination of criteria to apply to Torii contracts.
• It can be especially helpful for effective renewal management. For example, you can trigger a workflow when a contract with more than 5 licenses that was planned to be renewed is approaching its end date and to send yourself a reminder to renew it.
  

Workflows will only trigger more than once on the same object if the object was changed and no longer match the criteria but then changed again to match the criteria.