Skip to main content
Answered

Custom Actions API in Intercom always takes the first message as the input for the request body, regardless of subsequent messages

  • October 11, 2024
  • 2 replies
  • 48 views

I have a Custom actions API in which I have used the messageBody variable in my post request, however, when the flow is triggered on user’s message it always picks the very first msg that user sent in intercom chat widget and passes that to the post request and ignores all subsequent messages. In every subsequent request to my API the first message is being passed in the request body

Best answer by mateusz.leszkiewicz

Hi @Mubina waheed, It’s Mat from the Support Engineering Team 😀

It seem like an expected behaviour as far as I understood but I’ve created an Intercom conversation to look at your setup in details.
Our engineers will try to help you come up with the setup that will be suitable for your needs.

Please continue this thread there.

View original
Did this topic help you find an answer to your question?

2 replies

mateusz.leszkiewicz
Intercom Team
Forum|alt.badge.img+5

Hi @Mubina waheed, It’s Mat from the Support Engineering Team 😀

It seem like an expected behaviour as far as I understood but I’ve created an Intercom conversation to look at your setup in details.
Our engineers will try to help you come up with the setup that will be suitable for your needs.

Please continue this thread there.


  • Author
  • New Participant
  • 1 reply
  • October 14, 2024

But I want the messageBody variable to always hold the new user message instead of the first message. How to achieve this?
What i want is that whenever my workflow is triggered it should always pass that specific user msg in the post request of my custom actions api


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings