Trigger Narration, Trigger Stats & Overview Dashboard

This guide covers two visibility upgrades for triggers in workflows: Trigger Narration (human-readable filter summaries right on the trigger card) and Trigger Stats (Attempted / Matched / Unmatched, plus contact-level reasons). If you’re new to workflows or triggers, start with the Workflow Builder Walkthrough and A List of Workflow Triggers, then come back here.

What you can do

• Trigger Narration: See the “why” at a glance. Every trigger shows a human-readable narration of its filters/conditions on the trigger card.

• Trigger Stats: Measure what’s working in Stats View, each trigger displays Attempted, Matched, Unmatched and lets you drill into contact-level reasons (e.g., filter mismatch, missing data).

• Workflow Overview Dashboard: Surfaces trigger trends (match vs. unmatch, enrollments over time) so you can prioritize fixes.

Trigger Narration 

What it is

Each trigger card shows a simple and readable summary of its filters/conditions

This makes it easy to scan logic without opening the trigger.

How it works

• The narration appears below the trigger name.

• For complex triggers, you’ll see a compact summary with a “+X more” link.

• Click Details to open a panel with the full filter list.
  

Why it matters

Narration helps during audits, hand-offs  and reviews especially in large canvases, because you no longer need to open every trigger just to remember what it does.

Trigger Stats (Attempted / Matched / Unmatched)

What it is

Stats View shows per-trigger performance inside the workflow:

• Attempted — total contacts evaluated by the trigger

• Matched — contacts that met all conditions

• Unmatched — contacts that didn’t qualify

Click any stat to open the Trigger Stats Panel and see:

• Contact names, emails, and timestamps

• Match status

• Reason for Unmatch (e.g., value mismatch, missing field)

• Filters: date range, search by contact

Tip: This complements the broader workflow-level reporting available elsewhere in the app (e.g., list-level stats and communication metrics).

Quick example

You built a trigger “Contact Created” with a filter Contact Type = Customer. Stats show many Unmatched. In the panel you see:

• Received: lead

• Expected: customer
  Update the filter or your data standard and watch Matched rise on the next batch.

Use the Overview Dashboard to spot trigger problems across workflows

The Workflow Overview Dashboard gives you real time visibility into your automation performance.
See how your workflows are performing with match vs. unmatch counts, trend graphs, and trigger-level insights. You can get a holistic overview of all the workflow activity in this single dashboard..

From Automations → Overview you’ll see:

• Workflow Enrollments Over Time (weekly)

• Trigger Analysis Filter (filter by trigger type, form or survey)

• Matched vs. Unmatched Contacts

• Error Review Summary (quickly find workflows that encountered errors)
  

  
  

  

  
  

  

  
  

  

  
  

  
  
  
  

Troubleshooting & FAQs

Q.I don’t see narration on my trigger card.
Make sure the feature is enabled in Settings → Labs. If the trigger has many filters, look for the “+X more” link and click Details.

Q.My “Unmatched” count is high—what should I check first?
Open the Trigger Stats Panel and review Reason for Unmatch. Common causes: wrong value, missing field, or the wrong trigger selected. Review your trigger type and filters (compare against the trigger’s reference in the triggers catalog).

Q.Can I filter or search inside Trigger Stats?
Yes, use date range and search (by contact) within the stats panel.

Q.Does this change how triggers start workflows?
No. Triggers and actions still follow the standard workflow model: an event (trigger) starts the flow, then actions run in sequence. Narration and Stats only add visibility; they don’t change execution.

Q.Where can I see high-level performance across all workflows?
Use the Workflow Overview Dashboard (Automations → Overview) for enrollments, match vs. unmatch, and error review; then drill down to a specific workflow’s Trigger Stats.