0 online now · 0 in chat
AgentPlays Sign inJoin free

Automation & Routines · Other tools

Answer the messages a support bot missed during a server outage, then switch the catch-up off

Design an n8n recovery workflow for my support bot:
1. Trigger: poll [MONITOR] API every [N] minutes for my server's recent up/down history.
2. Start the backfill only after the server has been up for [N] minutes in a row.
3. Pull conversations from [CHANNEL] for the outage window and compare against the bot's reply log; keep only messages with no reply from the bot or a human.
4. Answer each one, fetching current order status and prices at reply time.
5. When the list is empty, deactivate the backfill workflow.
List the nodes, and how to avoid touching conversations a human is already handling.
Source: Dmitry Prozorovsky (via UptimeRobot) on x.com ·
Steps
  1. Watch the server from outside it, so the check still works when the server is down.
  2. After an outage, wait until the monitor history shows the server is stable again.
  3. Compare conversations with the bot's own records and reply only to messages that never got an answer.
  4. Look up live order status and prices at reply time, then switch the workflow back off.

Plays