Intro to Triggers
Last updated
Last updated
In this guide, we will discuss what triggers are and how to use them in association with both workflows and forms.
There are two ways to use a trigger currently
A trigger is used on any form input that requires a workflow. If you, on a form, click the "Dynamic" button then you absolutely must also create a trigger on the workflow associated.
A trigger is also used to run a workflow. This can either be in testing or in production.
Click into a workflow and across the top bar, there is a icon.
Pressing this brings up a small form for you to fill in. Note that you can have multiple triggers per workflow, such as a webhook and a trigger that runs when a ticket gets saved in the PSA.
The above image contains every setting for a trigger.
| Item | Description |
|---|---|
Name | The name of the trigger. Can be anything you want. |
Enabled | On or Off |
Organizations | Select all the orgs that exist within Rewst that may need to use this workflow. If you add a new client, they will have to be ticked in that workflow trigger. |
Integration Override | When a workflow is triggered by, and is thus running within the context of, a managed organization, by default they only have access to "their own" integrations/configurations (i.e. the managed org's Microsoft Graph tenant). In order to give the workflow access to integrations/credentials owned by the parent organization (i.e. the MSP) that default behavior must be explicitly overridden to say "regardless of who this workflow is running for, use the ConnectWise Manage integration belonging to the MSP". In the above image, the trigger allows your clients to use your PSA, RRM and Licencing integration. |
Trigger Type | There are a number of types to choose from, such as a webhook, form submission, ticket saved, M365 alerts etc |
Form | If your trigger type is a form submission, you would select the form that the workflow links to |
Once the trigger has been created on a workflow, it can be used on a form. NB: This MUST be an Options Generator workflow, whose requirements can be found here.
The above is a snippet from a form where a dropdown field has been selected and the output will be based on the workflow output. When running the form, so long as the client is added on the trigger and the trigger is set on the form, the workflow will run and the options put into the form field.
Want more practice?
