Skip to main content

Zapier trigger is too random

Sometimes, or actually most of the time, the Zapier event for new conversations is triggered before the conversation actually ends. I’ve tested it myself and sometimes it triggered while I still had the window open and hadn’t ended the chat.

The result is that Zapier only gets a part of the conversation. The end is often missing. This is bad as we are evaluating each conversation using a separate LLM and generate alerts for our customer service.

I know there is a balance to be struck. Some customers probably want the event triggered as quickly as possible. But I assume many customers appreciate getting the full convo in Zapier. I don’t know the mechanics, but if there is a timeout, maybe you can experiment with a longer setting. Or make it customizable.

3 comments

Log in to comment and vote

Comments3

  • Fabian Mösli

    •

    Mar 12, 2025

    This is still a big problem. We are often missing half the conversation in the post-processing because Chatling just fires the Zapier event whenever it wants. It should wait at least 5 minutes. Better yet would be to make it configurable.

    • Ali Mahdi

      Team•

      Mar 13, 2025

      Hi Fabian, the current timeout is 5 minutes. We’ve now increased it to 15 minutes. Let me know if this helps.

  • Fabian Mösli

    •

    Jan 3, 2025

    Has the team had a look at this one?

    Does anyone else have similar experiences?

    Sometimes the Zapier trigger even fires BEFORE the chatbot has answered! Looks like it triggers when the window loses focus? At least sometimes.