This table is a list of all triggers by category. To search for a definition quickly, press CTRL + F (Command + F on a Mac) on your keyboard and type in the name of the trigger to jump directly to it in the table.
|
CATEGORY |
TRIGGER |
EXPLANATION |
NOTES |
|
Client/Lead |
Client cancelled |
Runs when a client is cancelled |
|
|
|
Client source updated |
Runs when a client source is updated |
|
|
|
Client was created |
Runs when a client is created |
|
|
|
Client was reactivated |
Runs when a client is reactivated |
|
|
|
Contract is about to expire |
Checks for contracts expiring in [x] number of days |
This trigger allows you to set [x] number of days before the contract expires. This trigger runs once a day in search of contracts that expire within the specified number of days. |
|
|
Credit card charge failed |
Runs when a credit card charge fails |
This trigger looks at failed charges attempted through the invoice list. |
|
|
Credit card is about to expire |
Checks for cards expiring in [x] number of days |
This trigger allows you to set [x] number of days before the card expires. This trigger runs once a day in search of cards that expire within the specified number of days. |
|
|
Credit card was updated |
Runs if the credit card on file for the Account was updated |
|
|
|
Has opted in for emails |
Runs if the client/lead opted in for emails |
Opt-in is set by sending an opt-in email. |
|
|
Lead cancelled |
Runs when a lead is cancelled |
|
|
Lead was converted to client |
Runs when a lead is converted from a lead to a client |
||
|
Lead was created |
Runs when a lead is created |
||
| Date |
Run on client since date |
Runs on the client since date |
This trigger runs yearly (unless there is a stop condition). |
|
Run on custom field date |
Runs on the selected custom field date |
The custom field type must be set to date. | |
|
Run On Date |
Runs on the specified date |
This trigger runs yearly (unless there is a stop condition). | |
|
Run on day of week |
Runs on the specified day of the week |
This trigger runs yearly (unless there is a stop condition). | |
|
Run on time range |
Runs on the specified time range |
This trigger runs yearly (unless there is a stop condition). | |
| Estimate |
Estimate was created |
Runs when an estimate is created |
|
|
Estimate was lost |
Runs when an estimate is marked as lost |
||
|
Estimate was sent |
Runs when an estimate is marked as sent |
||
|
Estimate was won |
Runs when an estimate is marked as won |
||
| Form |
Form was submitted |
Runs when a form is submitted |
Be sure to select a form through the trigger. |
| Invoice |
Invoice past due |
Checks for invoices that are past due |
This trigger runs once a day in search of invoices that are past due. |
|
Invoice was created |
Runs when an invoice is created |
This trigger will pick up invoices created manually instantly, while invoices created from completed jobs will be picked up the following day. | |
|
Invoice was paid |
Runs when an invoice is marked as paid |
||
| Job |
Drive time started |
Runs when a resource uses the mobile app to drive to a visit
Note: The user must select the driving status to trigger an automation
|
This trigger only works with the Legacy app. Team app users will be included in the future. |
|
Job was cancelled |
Runs when a job is cancelled |
This trigger looks at master recurring jobs and master package jobs. | |
|
Job was created |
Runs when a job is created |
This trigger looks at the master job. | |
|
Package was created |
Runs when a package is created |
This trigger looks at the client package. | |
|
Visit date changed |
Runs when the visit date is changed |
This trigger looks at the visit occurrence. | |
|
Visit moved to waiting list |
Runs when a visit is moved to the waiting list |
This trigger looks at the visit occurrence. | |
|
Visit was cancelled |
Runs when a visit is cancelled |
This trigger looks at the visit occurrence. | |
|
Visit was completed |
Runs when a visit is marked as completed |
This trigger looks at the visit occurrence. | |
|
Visit was dispatched |
Runs when a visit is dispatched |
This trigger looks at the visit occurrence. | |
|
Visit was skipped |
Runs when a visit is marked as skipped |
This trigger looks at the visit occurrence. | |
| Tag |
Tag was added |
Runs when the specified tag is added to a client/lead |
|
|
Tag was removed |
Runs when the specified tag is removed from a client/lead |
||
| Ticket |
Calendar Event Completed |
Runs when a Calendar Event is marked as complete |
|
|
Calendar Event Created |
Runs when a Calendar Event is created |
||
|
Calendar Event Dispatched |
Runs when the status of a Calendar Event is changed to "dispatched" |
||
|
Calendar Event Skipped |
Runs when a Calendar Event is marked as skipped |
||
|
Ticket past due |
Runs when a Ticket becomes past due |
This trigger runs once a day in search of Tickets that are past due. | |
|
Ticket was closed |
Runs when a Ticket is marked as closed |
||
|
Ticket was created |
Runs when a Ticket is created |
||
|
Ticket was reopened |
Runs when the status of a Ticket goes from closed to open |
Trigger type. For example, Invoice Merge Tags only work with Invoice Triggers. They cannot
be mixed. For example, you could not use an Invoice Merge Tag with a Job Trigger.