Triggers

Every event type that can start an automation workflow.

IntermediateownermanagerUpdated 2026-04-23

Triggers

A trigger is the event that starts a workflow. When the event fires and any entry conditions pass, a new run is created and the workflow begins executing.

Each workflow has exactly one trigger. You choose the trigger in Step 1 of the wizard builder or by placing the trigger node in the visual builder.


Trigger Categories

Triggers are grouped into categories based on the area of your business they relate to.

Lead Activity

TriggerFires When
Lead CreatedA new lead is added to your account from any source
Lead Status ChangedA lead's status changes (e.g., new to contacted)
Lead Source MatchA lead comes in from a specific source you configure

Estimates

TriggerFires When
Estimate CreatedA new estimate is saved
Estimate SentAn estimate is delivered to the customer
Estimate ViewedThe customer opens the estimate link
Estimate AcceptedThe customer signs and accepts
Estimate DeclinedThe customer declines the estimate
Estimate ExpiredThe estimate passes its expiration date without a response

Jobs

TriggerFires When
Job CreatedA new job is created (usually from an accepted estimate)
Job Status ChangedA job transitions to a new status (you pick which status)
Job CompletedA job is marked as completed
Job AssignedA job is assigned to a crew member or rep

Invoicing

TriggerFires When
Invoice CreatedA new invoice is generated
Invoice SentAn invoice is delivered to the customer
Invoice PaidPayment is received for an invoice
Invoice OverdueAn invoice passes its due date without payment

Appointments

TriggerFires When
Appointment ScheduledA new appointment is booked
Appointment UpcomingA configured number of minutes before the appointment time
Appointment CancelledAn appointment is cancelled

Communication

TriggerFires When
SMS ReceivedAn inbound text message is received
Email ReceivedAn inbound email reply is received
Call ReceivedAn inbound phone call hits your workspace telecom number
Call AnsweredA call is answered and connected
Missed CallAn inbound call is not answered
Voicemail ReceivedA voicemail recording is captured
Call CompletedA call finishes with final status and duration

System

TriggerFires When
Manual TriggerYou manually enroll a contact from the workflow detail page
Webhook ReceivedAn external system sends data to your webhook URL
Recurring ScheduleOn a cron schedule you define (daily, weekly, monthly, etc.)

Trigger Configuration

Some triggers need extra configuration to tell the engine exactly when to fire.

Job Status Changed

When you select this trigger, a dropdown appears asking which status transition should activate the workflow. For example, you might choose "en_route" to send the customer a text that the crew is on the way.

Appointment Upcoming

This trigger asks for a number of minutes before the appointment and which appointment type you want to target:

  • Lead or Estimate for site visits, estimate appointments, and pre-job sales visits
  • Job for scheduled service work
  • 1440 minutes (24 hours) for a day-before reminder
  • 120 minutes (2 hours) for a same-day heads-up

Phone Triggers

Phone triggers fire from the shared telecom number tied to your workspace.

  • Call Received is the first event, fired as soon as CE Pro accepts the inbound call.
  • Missed Call fires when the office forwarding leg is not answered.
  • Voicemail Received fires after the active provider provides the voicemail recording. In Esendex Phase 1, inbound voicemail recording playback is not live yet.
  • Call Answered fires when a call leg is answered.
  • Call Completed fires only when the call actually completes, not when the call ends as no-answer, busy, failed, or canceled.

For phone triggers, the workflow context can include caller number, destination number, duration, voicemail transcript, and any confidently matched client or estimate.

Lead Source Match

Enter the lead source name that should activate the workflow. This is useful when you want different follow-up flows for Google Ads leads versus referral leads.

Recurring Schedule

Define a cron schedule and an audience query. The engine evaluates the audience query to find matching contacts, then creates one run per contact. Use this for things like quarterly win-back campaigns or monthly check-ins.


One Trigger Per Workflow

Each workflow can only have one trigger. If you need the same set of steps to run for different events, you have two options:

  1. Duplicate the workflow and change the trigger on the copy.
  2. Use the "Enroll in Workflow" step from one workflow to chain into another.

Tips

  • Start with the most common triggers: Lead Created, Estimate Sent, and Job Completed. These three cover the majority of field service automation use cases.
  • Test your trigger using the Test Run button on the workflow detail page before activating. It simulates the trigger with mock data so you can preview what happens.
  • Recurring schedule triggers are powerful but should be used carefully. Make sure your audience query is scoped correctly so you do not message customers who have opted out or are already in active workflows.

If you are replacing a legacy Follow-Up Sequence, activate the new workflow on the same trigger so CE Pro routes new events through the automation engine instead of sending duplicate outreach from both systems.

Was this article helpful?

Still need help? Contact support