Did You Miss the Thread and Neglect to Respond?

Help
1

This topic was automatically generated from Slack. You can find the original thread here.

Hey there! Still did not receive any reply. You didn’t miss the thread, did you? :face_holding_back_tears:

2

Could you share the configuration for the Intercom POST request?

3

Sure! Post - https://api.intercom.io/conversations/search

{
 "query":  {
    "operator": "AND",
    "value": [
      {
        "field": "waiting_since",
        "operator": "<",
        "value": "{{steps.GetDayAgoTimestamp.$return_value}}"
      }, 
      {
        "field": "open",
        "operator": "=",
        "value": true
      },
      {
        "field": "admin_assignee_id",
        "operator": "!=",
        "value": "5575723"
      },  
      {
        "field": "admin_assignee_id",
        "operator": "!=",
        "value": "5403786"
      },  
      {
        "field": "admin_assignee_id",
        "operator": "!=",
        "value": "5400605"
      } 
                   
    ]
  }
}

image.png
image.png1220×850 28.5 KB

image.png
image.png1197×806 26.8 KB

image.png
image.png1194×1107 35.7 KB

4

I’m not sure if this is the problem, but could you try removing the quotes around {{steps.GetDayAgoTimestamp.$return_value}}. It looks like an Intercom Conversation’s waiting_since attribute is an integer or null.

5

Nah, that’s not an issue, coz it’s working just fine in other similar WFs and, moreover, it is working normally when I start the trigger manually.

6

Hmm, that seems frustrating. I wonder if it’s an issue with that specific workflow or deployment. Would you mind trying to copy the workflow then deploy it and see if that works?

7

Tried. Didn’t help.
I am planning to manually duplicate each step into new WF. Also, going to try converting this “GetConversations” into js code step.

8

Oh. It has just started to work normally. With no changes from my side.
Interesting.