What does this do?
A trigger is what starts a Process. There are various types of triggers: manual trigger, webform triggers, email triggers, scheduled triggers, and integration triggers.
How do I use this functionality?
In order to begin a Process run, a trigger needs to be started. You can either head directly to Start a Process in the left menu and select the Process you'd like to start, or you can create a trigger under the "Triggers" section of the menu.
How do I set up a trigger?
- Webform Trigger
- A Process can be created by someone completing an online form
- Create the fields for this trigger on a template level
- The trigger can always be found at the URL you create
- Email Trigger
- Can email address can be created to start a specific Process
- When someone sends an email to the designated email address, it kicks off the Process
- Scheduled Trigger
- You can set up a schedule for when you'd like the Process to automatically start
- For example: every Monday, once a month, every two weeks, Friday at 10:00am
- Integration Trigger
- Integration triggers are only available if you have the specific integration
- If you do not have the integration, the option for the trigger will not show up
- Before you create a trigger, the process template must be created first.
- When a template requires multiple triggers, it may be helpful to add any initial fields to 2 locations: 1. Template level fields and 2. Within an Assign Task to a Person action set as the first task within the template. The action will need a condition to ensure it is only opened when specific triggers occur. This duplication will allow the template to be triggered in various ways. Example: If a process requires a webform trigger and an email trigger, the webform will require template level fields, while a task to request the fields is best for the email trigger.
- Creating an automatic trigger is always preferential over manually starting the process via Start a Pushbot within Catalytic as no one must remember to start the process.
- Many triggers will assign the run owner as the process owner. If you would like to update the run owner for each process run, add a Pushbot: Update Owner action within your template.