Triggers are used as the very first node in a workflow, they're what tells Ploy to kick off that workflow and start executing the nodes below this first trigger node. We have an ever growing number of triggers which are outlined and explained in this article, some of these include:
| Category of Trigger | Description |
|---|---|
| App Triggers | App Triggers are all based off something happening with or to an application in your Ploy environment. Currently this includes: |
| • When a new application is discovered | |
| • When a tag is added to an app | |
| • When an app status changes | |
| Member Triggers | Member Triggers are all based off something happening with or to an member in your Ploy environment. Currently this includes: |
| • When a member becomes inactive | |
| • When a new member account is discovered | |
| • When a member's end date is updated | |
| • When a member's start date is updated | |
| Commercial Triggers | Commercial Triggers are all associated with the commercial aspects of SaaS, whether this is managing renewals, removing unused licenses or identifying receipts via our email scanning. Current triggers include: |
| • When a user hasn't signed in for 90 days | |
| • When a new receipt is discovered | |
| • When a SaaS is "x" period away from renewal | |
| Access Triggers | Access Triggers, as the name suggests is all about Ploy's access these include: |
| • When an access review status is changed | |
| • When access is requested | |
| Misc Triggers | Misc Triggers are ones that don't fit into a specific trigger category but are still really powerful, the article dives into these in more detail, but they include: |
| • Schedule (which schedules when the trigger happens) | |
| • Survey response received from an employee |