Skip to main content

I decided to upgrade to version 2, which made any Chatling integration with Zapier to break.

Bug Reports

I have Chatling integrated with Slack. It's a simple one that sends me a message on Slack when a new conversion starts. It includes the content of the conversation, rating, and so on.

Now, the Zapi is firing all the time (when there are no conversions), with, of course, no information about a conversion happening. It's firing what seems to be completely random.

I went ahead to edit the Zap. The event is still the same—new conversation. 

I then refreshed records (from Chatling) and repeated the same process.

This leaves me with two questions: 

  1. Why does the Zap keep firing when there are no new conversations?

  2. Why is the whole conversation lumped into 'Message Text', where the delimiter is a comma? That's the least genius move I've seen in a long time. It separates the user inquiry and the answer from the bot with a… comma. You could have used literally ANY character, but you chose a comma. It makes no sense at all.

Posted by Anders Eilertsen ·
Status: Completed5 comments

Log in to comment and vote

Comments5

  • Ali Mahdi

    Team•

    Mar 12, 2024

    Hi Anders,

    Sorry for the inconvenience caused.

    We're aware of the bug and my team is working on fixing it. I'll inform you as soon as the problem is resolved.

    • Anders Eilertsen

      •

      Mar 12, 2024

      Hi,

      Thank you for the prompt reply. It's reassuring to know that you are aware of the issue and that it's being actively addressed. I appreciate your team's efforts to resolve this and look forward to being informed once the problem has been fixed.

      • Ali Mahdi

        Team•

        Mar 12, 2024

        Hi Anders, the issue has been resolved. Please check and let me know if there are any problems.

        • Anders Eilertsen

          •

          Mar 13, 2024

          Hi,

          First of all, thanks for looking into this matter.

          It seems the Zap is not firing randomly anymore, which is great!


          What is not ideal is (as I mentioned in my initial post) that all messages, both from the user and bot, are lumped together in 'Message Text', where the delimiter between the text input from the user and the answer from the bot is a comma (,).

          You cannot format this as a user (inquiry) or bot (answer) to structure the conversation.


          When choosing a delimiter to separate user input from bot responses, it's crucial to select a character or combination of characters that are unlikely to appear naturally in the conversation.

          Commas are used in sentences to separate clauses or items in a list or indicate a pause. However, if a comma is used as a delimiter, it would not be easy to distinguish between it and a regular comma used in the text.


          Using a single character, like a comma, as a delimiter provides limited options for structuring the user and bot.


          It would be better to use a unique character or a combination of characters rarely used in normal text. Some examples of better delimiters include:

          1. Pipe symbol (|)

          2. Tilde (~)

          3. Triple asterisks (***)

          4. Double hash (##)

          5. Curly braces with a specific pattern, like {user} or {bot}

          • Ali Mahdi

            Team•

            Mar 13, 2024

            Hi Anders, that’s being done by Zapier. Our system sends the entire message as a JSON object to Zapier.

            There’s nothing much we can do from our side unfortunately.