Know when a Zap stops running
Add a last step to your Zap so you're alerted when it stops firing, gets turned off, or loses its connection.
When a Zap's connection expires or Zapier turns it off, there's often no error email — just silence. Add a heartbeat as the final step and you'll hear about the silence.
Option A: Webhooks by Zapier (works today, paid Zapier plans)
- Add a final step: Webhooks by Zapier → POST.
- URL:
https://diditrun.app/p/YOUR-TOKEN - Payload Type: json. Add data fields such as
items(map the number of records processed) andtext(a summary field).
Option B: Email by Zapier (coming soon)
Once email check-ins launch, you'll be able to use Email by Zapier → Send Outbound Email to your watch's own address instead. That isn't live yet, so use Option A today.
Which Zapier plans work?
The heartbeat is an extra final step, so it needs a multi-step Zap. Zapier's Free plan limits Zaps to two steps and doesn't include Webhooks by Zapier, so you need a paid Zapier plan (or Zapier's 14-day trial) today.
Pick the right schedule
- For Schedule by Zapier Zaps, use the same schedule on the watch ("every weekday at 8:00am", grace 15 min).
- For event-driven Zaps (new form entry, new order), use the longest normal quiet period — e.g. "at least once every day by 6pm" — so you hear about it when the events stop.
Tip: catch "ran but did nothing"
Add Required keyword (e.g. a field you expect to always be present) or Minimum body size, so a Zap that runs with blank data raises an empty alert.