Zapier zap worked before but stopped triggering this week
#17 In ProgressMy reply-triggered Zap has worked fine for months and just stopped firing about 4 days ago. Nothing changed on my end that I know of.
The most common cause we see for this is the same one from an earlier reply-detection thread — reply detection getting toggled off on the campaign, or the sending mailbox's connection needing re-authorization. Can you check Campaign > Settings > Reply Detection on the relevant campaign, and also Settings > Sending to confirm the mailbox still shows as “Connected” rather than needing reauth?
Both of those look fine actually — reply detection is on, mailbox shows connected. Replies ARE showing up in my SubsiMail inbox, just not triggering the Zap anymore.
Okay, that rules out the usual cause then — if replies are landing in your inbox but Zapier isn't picking them up, the webhook URL Zapier is listening on may have gone stale (this can happen if you ever reconnected or re-authorized the Zapier integration itself, which regenerates the webhook). Can you go into Zapier, open the Zap, and try re-selecting the trigger step to force it to re-fetch the current webhook URL? I'd also like to check our webhook delivery logs for your account in the meantime — can you confirm the approximate time of a reply that should have triggered it but didn't?
Sure, here's one from yesterday around 2:15pm my time (I'm on Eastern). Re-selecting the trigger step in Zapier didn't seem to change anything either, still not firing.
Log in to reply to this ticket.