In a CRM setup, Busabase holds customer statuses and n8n sends scheduled follow-up emails. Once a customer replies, books an appointment, or unsubscribes, their remaining reminders should stop.
How would you connect that? Read the latest Busabase status immediately before each send, or cancel queued tasks in the external workflow when the status changes? The goal is to stop that customer's follow-ups while everyone else's sequence continues.
Use both checks. In Busabase, keep the customer's current follow-up status, subscription/opt-out state, and a follow-up round or version. When n8n is about to send an email, read that latest approved state again. Send only if the customer still needs this round's follow-up and has not replied, booked, or unsubscribed; if the lookup fails or the status is unclear, pause rather than sending. A pending Change Request is not yet the current record until it is merged.
When a reply, booking, or unsubscribe arrives, also try to cancel that customer's queued n8n work by its customer/round identifier. Keep the pre-send check as the final guard because cancellation can arrive late. Record a send key for each planned message so a retry cannot send it twice, and carry unsubscribes into the sending service's suppression list. Updating Busabase alone does not cancel an external queue. This related discussion walks through the same setup in Chinese. Are you using n8n Wait nodes or a scheduled scan of customers due for follow-up?
Sign in to join the discussion. Reading is always open; you only need an account to post.
Sign in