The Trigger Condition is what starts an automation. When you create one under Automations, you choose the trigger, a Run Time and an Action. You can also run another automation afterwards.
Run times
- Most triggers run Instantly, or 2 minutes, 15 minutes, or 1, 3, 5, 7, 15 or 30 days after the trigger happens.
- “Before” triggers (Before a Visit / To-do / Meeting / Equipment Maintenance Happens, and Before Invoice Becomes Past Due) run 1, 2 or 3 days before. They can’t run instantly or after.
- Run at a Certain Time uses the Date & Time you choose instead of a run time.
If you pick a run time that doesn’t fit the trigger, you’ll see “The selected run time is not supported for this automation” when you save.
Actions
Text or email the company owner, the customer or an employee, or add or remove a tag.
- Push Notification Reminder only works with Before a To-do Happens.
- Add a Tag and Remove a Tag can’t be used with A Tag is Added, any Estimates trigger, Invoice is Sent, Before Invoice Becomes Past Due, Invoice Becomes Past Due, Payment Made on an Account or Payment Receipt Sent.
- Texts are only sent during your texting hours.
Triggers
The Trigger Condition dropdown groups the triggers like this:
Scheduled
| Trigger | Runs when |
|---|---|
| Run at a Certain Time | At the date and time you set, for example a one-time message to all customers |
Visits
| Trigger | Runs when |
|---|---|
| Visit is Added | A visit is added to the schedule |
| Before a Visit Happens | 1–3 days before a visit (visit reminders) |
| Visit is Completed | A visit is marked complete |
| Note added to visit | A note is added to a visit |
Tasks and Meetings
| Trigger | Runs when |
|---|---|
| To-do is Added / Meeting is Added | A to-do or meeting is added to the schedule |
| Before a To-do Happens / Before a Meeting Happens | 1–3 days before it |
| To-do is Completed / Meeting is Completed | It’s marked complete |
Equipment Maintenance
| Trigger | Runs when |
|---|---|
| Equipment Maintenance Added | A maintenance item is added |
| Before an Equipment Maintenance Happens | 1–3 days before it’s due |
| Maintenance is completed | It’s marked complete |
Estimates
| Trigger | Runs when |
|---|---|
| Estimate is Sent | An estimate is sent |
| Estimate is Accepted | The customer accepts |
| Estimate is Declined | The customer declines |
| Estimate Changes are Requested | The customer requests changes in their portal |
| If an Estimate is Accepted or Declined | Either one happens |
| If an Estimate is not Accepted or Declined | A sent estimate has had no answer after the run time you choose (follow-up reminders) |
Invoices and Level Billing
| Trigger | Runs when |
|---|---|
| Invoice is Sent | An invoice is sent |
| Before Invoice Becomes Past Due | 1–3 days before the due date |
| Invoice Becomes Past Due | An invoice passes its due date |
| Invoice Paid by Auto-Charge | Auto-Charge pays an invoice |
| Level Billing Agreement is Ending (Final Invoice) | A level billing agreement reaches its final invoice |
Payments
| Trigger | Runs when |
|---|---|
| Payment Made on an Account | Any payment is recorded: online, by charging a saved card, or entered by your team |
| Payment Made With Tip | A payment includes a tip |
| Payment Made in the Portal by Customer | The customer pays in their portal |
| Payment Added to an Invoice by a LawnPro User | Someone on your team adds a payment |
| Payment Receipt Sent | A receipt is sent |
| Card on File is Declined | A charge to a saved card fails |
Customers and Tags
| Trigger | Runs when |
|---|---|
| New Customer is Added | A customer is added |
| Service is Suspended (Past Due) | A customer’s service is suspended for a past due balance (see Service Suspension in Invoices, Estimates & Receipts Settings) |
| Service is Reinstated | Their service is reinstated |
| A Tag is Added | A tag you choose is added. Pick the Tags Type (All Tags, or tags used with Assets, Events, Customers, Vendors, Crews or Forms) and the Tags. |
| Work Request is Received | A work request comes in |
| Property is Not Serviced | A visit is marked Not Serviced |
Payment Methods (Cards and Bank)
| Trigger | Runs when |
|---|---|
| Customer Added a Credit Card / Customer Removed Credit Card | The customer adds or removes a card in their portal |
| Customer Added Bank Account / Customer Removed Bank Account | The customer adds or removes a bank account |
| Customer Added Bank Account But ACH not Verified | A bank account is added but not yet verified |
| Customer Allowed Auto-Charge on Card | The customer gives permission to auto-charge their card |
Time Tracking
| Trigger | Runs when |
|---|---|
| Job Timer Started / Job Timer Stopped | An employee starts or stops a job timer |
Reviews
| Trigger | Runs when |
|---|---|
| A Customer Has Not Left a Review | A customer hasn’t left a review yet |
| A Customer Left a Review of Any Rating (0-5 Stars) | Any review comes in |
| A Customer Left a Review With a Rating of 0 to 3.5 Stars | A low review comes in, for example to alert you |
| A Customer Left a Review With a Rating of 4 to 5 Stars | A good review comes in, for example to ask for a public review |
Text Messages
| Trigger | Runs when |
|---|---|
| When a New Text Message is Received | A customer texts you |
Review Before Execution: check this on an automation to approve each run before it goes out. It’s included on Grow and higher.