What is an App Trigger?
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.
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
New app discovered
1. How New app discovered triggers
This will trigger when Ploy has discovered a brand new app in your environment. Let's say there is a brand new SaaS tool that an employee has signed up to that has never been used in your organisation
2. Configuration
You have several options to configure the New App Discovered which act as a filter in the work flow. Once selected the child nodes later on in your workflow will only be executed if the app matches the configuration you've set.
Configuration Option | Description |
Category | What type of category is the application e.g. Finance, Document Management, Communication etc... |
Permission Risk Score | Whether the app has high, medium or low OAuth permissions granted by the user, these are pre-set by Ploy |
Type | Whether the app is a SaaS or Non-SaaS application |
Status | Whether the app is sanctioned, unsanctioned, archived etc.. |
3. Example Workflow
The workflow below uses a new app trigger (renamed in this example to high risk app) and then proceeds to alert security via a slack notification and send out a Slack survey to the employee asking if they are sharing customer data. If they respond yes then the high risk OAuth Token will be revoked via the Revoke OAuth Token action.
Tag added to app
1. How Tag added to App triggers
Throughout Ploy you can add tags to apps to help you track different aspects, whether this is compliance, finance or IT related. When a tag is added to an application by a user in Ploy this will trigger the workflow you have created.
2. Configuration
There is one configuration for the tag added to app trigger which enables you to select the tag to use for this (as a filter).
Configuration Option | Description |
Tag | Which tag would you like the workflow to trigger for. This acts as a filter so the workflow will only trigger for the tag you select |
3. Example Workflow
App status change
1. How App status change triggers
This triggers when the status of an app is changed, you will select which status change you would like to be in the configuration (outlined below).
2. Configuration
There is one configuration for the app status change trigger which enables you to select the status the app is changed to
Configuration Option | Description |
Status | What status would you like the app to be change to in order to trigger this workflow e.g. if selection "sanctioned" the workflow will trigger when an app is changed from something to sanctioned |
3. Example workflow
