Automated Celigo Integration Failure Alerts
Every hour, WebRun opens Celigo, checks every integration flow's last run, checks Google Calendar for the ops team's next open working slot, and messages the team on WhatsApp with any flow that failed and a suggested fix window.
How do I catch a failed Celigo integration flow before records back up?
WebRun checks every Celigo integration flow every hour, reads Google Calendar for the ops team's next open working slot, and messages the team on WhatsApp with any flow that failed and a suggested fix window. Integration teams catch a broken flow before unsynced records back up across connected systems.
- A failed flow is known within the hour, not after records pile up
- A suggested fix window means the team doesn't have to hunt for time
- Quiet hours stay quiet, only real failures generate a message
Built for operations teams · integration engineers · ecommerce operations teams
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
celigo.comin a real browser with your saved login - no setup, no API keys. -
1
Celigo - check flow run status
WebRun opens Celigo to check flow run status. - Open Celigo and check every integration flow's last run
- Read the status and error for any flow that failed
- Note which systems the flow connects
Done when Every flow's last run status is checked.
-
2
Google Calendar - find an open fix window
WebRun opens Google Calendar to find an open fix window. - Open Google Calendar and find the ops team's next open working slot
- Confirm no one is already booked for that time
- Note the slot as the suggested fix window
Done when An open fix window is identified for any failed flow.
-
3
WhatsApp - message the team
WebRun opens WhatsApp to message the team. - Message the ops team group on WhatsApp
- List any failed flow with its error and connected systems
- Include the suggested fix window
Done when The team knows about any failed flow and when to fix it.
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
Does WebRun rerun the failed flow?
No. It only reads flow status from Celigo and reports what failed. Rerunning or reconfiguring a flow stays a manual step.
Will the team get a message every hour even with no failures?
No. The WhatsApp message only goes out when a flow actually failed, so quiet hours stay quiet.
How is the fix window chosen?
From the ops team's own Google Calendar. WebRun only suggests a genuinely open slot, it never books anything on your behalf.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.