Workflow Triggers

A trigger is the event that starts your workflow. JustCall monitors these events in real time and launches the workflow within seconds of the event occurring.

Available Triggers

call.completed

Fires when any call (inbound or outbound) ends normally.

Data provided: caller number, agent name, call duration, recording URL, disposition code, tags, call direction, JustCall number.

call.missed

Fires when an inbound call goes unanswered by any agent or ring group.

Data provided: caller number, called JustCall number, ring duration, date and time, queue name (if applicable).

call.answered

Fires when an inbound call is picked up by an agent.

Data provided: caller number, agent name, JustCall number, ring time, call direction, queue wait time.

sms.received

Fires when an inbound SMS or MMS arrives on any JustCall number.

Data provided: sender number, message body, media URLs (for MMS), JustCall number, contact name (if matched), conversation ID.

sms.sent

Fires after an outbound SMS or MMS is sent by an agent or automation.

Data provided: recipient number, message body, media URLs, JustCall number, agent name, send status.

voicemail.received

Fires when a caller leaves a voicemail.

Data provided: caller number, voicemail recording URL, voicemail duration, transcription text, JustCall number, date and time.

contact.created

Fires when a new contact is added to JustCall — manually, via import, or through an integration sync.

Data provided: contact name, phone number, email, company, source (manual, CSV, CRM sync), custom fields.

How Triggers Work at Runtime

1. The event occurs (for example, a call ends).
2. JustCall checks all active workflows for a matching trigger.
3. If multiple workflows share the same trigger, each one runs independently.
4. Trigger data is passed into the workflow and becomes available as merge fields in conditions and actions.

Choosing the Right Trigger

Limits

• Each workflow has exactly one trigger. To react to multiple events, create separate workflows.
• Trigger evaluation adds less than two seconds of latency before the first action fires.
• Duplicate triggers across workflows are allowed and do not interfere with each other.

Select your trigger thoughtfully — it determines every condition and action that follows.