"IF" node, "Not equal" operation doesn't work

For some reason, when 2 equal values are compared, they are considered not equal.

Hi @Artego,

If you check the JSON coming out of the node is it a number or a string? If you can share the JSON from the previous node we can give it a quick test.

Hi @jon
It’s a number

[
   {
      "v":1,
      "matches_filters":{
         "current":[
            
         ]
      },
      "meta":{
         "action":"added",
         "change_source":"app",
         "company_id":3897065,
         "host":"sumsub.pipedrive.com",
         "id":114922,
         "is_bulk_update":false,
         "matches_filters":{
            "current":[
               
            ]
         },
         "object":"activity",
         "permitted_user_ids":[
            6098862,
            7870729,
            9383196,
            9383232,
            11322694,
            11435040,
            11537238,
            11537242,
            11590820,
            11987466,
            11999022,
            12037509,
            12043080,
            12060492,
            12073395,
            12078528,
            12094995,
            12172173,
            12194820,
            12215685,
            12221145,
            12239001,
            12257346,
            12257364,
            12606601,
            12670676,
            12701762,
            12716227,
            12767927,
            12827030,
            12875848,
            12898654,
            12900972,
            12919331,
            12939893,
            12954578,
            12972563,
            12994263,
            12994274,
            12998919,
            13009589,
            13020193,
            13038101,
            13131304,
            13133878,
            13140247,
            13140258,
            13155328,
            13271529,
            13308390,
            13338937,
            13384114,
            13393618,
            13417048,
            13434032,
            13481156,
            13489758,
            13516510,
            13616962,
            13616984,
            13740217,
            13791609
         ],
         "pipedrive_service_name":"automation-phpapp-proxy",
         "timestamp":1656689860,
         "timestamp_micro":1656689860675980,
         "trans_pending":false,
         "user_id":11590820,
         "v":1,
         "activity_notifications_language":null,
         "send_activity_notifications":false,
         "webhook_id":"60951"
      },
      "current":{
         "last_notification_time":null,
         "location_street_number":null,
         "type_name":"Ping",
         "reference_id":null,
         "location_route":null,
         "public_description":null,
         "notification_language_id":null,
         "subject":"The deal owner has changed",
         "updates_story_id":877342,
         "type":"ping",
         "project_id":null,
         "deal_title":"Definancy",
         "id":114922,
         "deal_id":35646,
         "busy_flag":null,
         "person_id":29060,
         "owner_name":"Peter Ortiz",
         "attendees":null,
         "person_name":"Rogério Ferreira do Ó",
         "project_title":null,
         "rec_rule_extension":null,
         "done":true,
         "created_by_user_id":11590820,
         "location_sublocality":null,
         "rec_rule":null,
         "location_admin_area_level_2":null,
         "user_id":11590820,
         "location_admin_area_level_1":null,
         "org_id":25415,
         "conference_meeting_client":null,
         "note":null,
         "due_time":"",
         "rec_master_activity_id":null,
         "location_country":null,
         "active_flag":true,
         "duration":"",
         "location_postal_code":null,
         "update_time":"2022-07-01 15:37:40",
         "update_user_id":null,
         "lead_title":null,
         "source_timezone":null,
         "person_dropbox_bcc":"[email protected]",
         "conference_meeting_id":null,
         "org_name":"Definancy",
         "location_locality":null,
         "assigned_to_user_id":11590820,
         "lead_id":null,
         "is_recurring":null,
         "participants":[
            {
               "primary_flag":true,
               "person_id":29060
            }
         ],
         "location_subpremise":null,
         "company_id":3897065,
         "due_date":"2022-07-01",
         "lead":null,
         "reference_type":null,
         "last_notification_user_id":null,
         "calendar_sync_include_context":null,
         "marked_as_done_time":"2022-07-01 15:37:40",
         "location_formatted_address":null,
         "series":null,
         "conference_meeting_url":null,
         "location":null,
         "deal_dropbox_bcc":"[email protected]",
         "add_time":"2022-07-01 15:37:40"
      },
      "previous":null,
      "event":"added.activity",
      "retry":0
   }
]

Another example here using String. I really don’t understand how IF node works sometimes

Hi @Artego

I see you have combine set to All in your original post’s workflow.
image
This might be what is causing your issue there. As all checks need to be true for it to go into the true branch.
With your last screenshot It doesn’t show the actual true values in the conditions. As it is comparing www.google.com to 360.cn, so this check might be broken because it isn’t checking the correct value.
If you can post that workflow as well I can have a look.

1 Like

Hi @BramKnuever
Yes, I do have combine set to ALL, however, the highlighted value doesn’t match but still passes as True.
As for the second example, I highlighted one of the items as there are 59 of them, that contains ‘google’ but the output was False, even though it was supposed to be True.

Hi @Artego

I know the IF node can be easy to make mistakes in. I have however never seen actual errors in the node itself. So it is probably just a tiny mistake you are overlooking. We cannot help you without the workflow and sample data.

@BramKnuever
I shared the workflow in the initial post and also commented the JSON coming out of the node that comes before the IF node.
The second examples I shared is very likely the same mistake I made. However, I don’t understand what’s wrong. The IF node is probably the easiest one to handle lol

Hi @Artego

The IF node is really easy idd, but is also easy to make small mistakes in.
I’ve tried your workflow and your data, and it goes to the false branch fine. So the first example, I am not sure why this would go wrong for you.
What version are you running? Maybe it is related to an old bug.

Hi @BramKnuever
Thank you for trying the workflow. Weird thing, I tried running it with a function and it worked fine, but with a real trigger, it doesn’t go to the false branch. Maybe it pulls the data wrong, I don’t know :frowning:

Hi @Artego

That is very strange idd. Something in the data is different then idd. Maybe the format or a space or something like that?

I think I’m getting closer to solution. However, still no luck. Found out that it only compares to the first item