Automated Iterable Journey Stall Alerts
Every morning, WebRun opens Iterable, lists the journeys currently live, reads how many users entered each one and how many messages went out in the last day, flags any journey that has stopped sending, posts the stalled list to Slack, and drafts an escalation email in Gmail for approval.
How do I know when an Iterable journey has stopped sending?
Every morning, WebRun opens Iterable, lists your live journeys, and reads how many users entered and how many messages went out in the last day. It flags any always-on journey with no sends since yesterday, posts the stalled ones to Slack, and drafts an escalation email in Gmail for approval.
- A silent welcome or winback journey is caught within a day
- Every live journey has a daily send count on the record
- No journey is paused, edited or republished by the run
Built for lifecycle marketers · CRM teams · growth marketers · marketing operations
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.iterable.comin a real browser with your saved login - no setup, no API keys. -
1
Iterable - check sends on every live journey
iterable.com
WebRun opens Iterable to check sends on every live journey. - Open Iterable and list every journey with a live status
- Read the users entered and the messages sent for each one over the last day
- Compare that against the same journey's normal daily volume
- Flag any journey with no sends since yesterday, and any whose volume dropped sharply
- Open the journey to see which node the users are sitting at, and note the template in use
- Pause nothing and edit nothing. WebRun reads the journey and leaves it running
Done when Every live journey has a send count for the last day and a normal or stalled verdict.
-
2
Slack - post the stalled journeys
slack.com
WebRun opens Slack to post the stalled journeys. - Post the stalled journeys to your lifecycle channel
- Name each journey, the last time it sent and the node users are stuck at
- List the healthy journeys as a count, so the post stays short
- Say nothing on a morning when every journey is sending normally
Done when The lifecycle team knows which journeys went quiet overnight.
-
3
Gmail - draft the escalation
gmail.com
WebRun opens Gmail to draft the escalation. - Draft an internal escalation email when a journey has been silent for more than one run
- Include the journey name, the silent period and the node users are waiting at
- Leave it in Drafts. WebRun never sends the email, and it never messages a customer
Done when A persistent stall has an escalation drafted and waiting for approval.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it send anything to customers?
No. WebRun reads journey metrics and reports internally. It never sends a campaign, edits a template or messages a customer.
Will it pause or restart a journey?
No. Pausing, editing and republishing stay with your team in Iterable. WebRun only tells you which journey stopped and where users are waiting.
What about journeys that are meant to be quiet?
Mark them as low volume once and WebRun compares against their own normal, so a seasonal journey is not reported as stalled every morning.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.