Trouble with Pabbly Router/Filter

[JustinPM123]

Your Workflow URL

https://connect.pabbly.com/v2/app/workflow/mapping/IjU3NjYwNTY0MDYzNDA0MzI1MjZkNTUzNzUxMzMi_pc

Consent to Access & Modify

I authorize Pabbly Support to log in to my account and make changes to the specified workflow for troubleshooting.

I'm having trouble with my Router/Filter. I initially setup the Router 7 Filters with simple, single parameters. And it worked. Now I am trying to edit the existing Filters and add more Filters, with multiple more specific parameters. While recapturing the Webhook, it looks like the data is coming through correctly. But after changing a Filter, saving, and sending a Webhook to test, the Filter says "Condition is false" when I have confirmed it is true. After viewing this in the Workflow History, I go back to edit the Workflow to confirm my settings, and sometimes the Webhook field will be missing data, the Name of the Filter will be reverted back to when it was cloned, and other various issues.

My goal is to check the Webhook data for 2 values: Event Type (original value that works as standalone), and Order Status ID. See attached screenshots for reference.
One is of the data received from the Webhook, the other is showing that the Filter does not see the Condition for the second parameter.

Currently, the Workflow is set to only "Condition: Event Type = order_update" to ensure that the Workflow executes.

Can you please tell me how to resolve this?

Thank you,

Justin M.

 

[ArshilAhmad]

Hi @JustinPM123,

The keys you receive in the trigger step change with each Order ID, which breaks the mapping.

Please disable 'Simple Response', then click on 'Re-Capture Webhook Response' and capture a new order in your trigger step. This should allow you to capture the order details in the form of a JSON. Once you’ve captured the order details in JSON format, do let us know. We’ll add a Code step to your workflow that will extract the keys without the Order IDs, ensuring they remain consistent.

 

[JustinPM123]

Hello @ArshilAhmad,

I had originally had the Webhook response set to Simple but then turned it off to see if that helped.
I will restore the setting to Simple Response and set the Code step to strip out the Order ID data, and test that configuration.

 

[ArshilAhmad]

Hello @ArshilAhmad,

I had originally had the Webhook response set to Simple but then turned it off to see if that helped.
I will restore the setting to Simple Response and set the Code step to strip out the Order ID data, and test that configuration.

If you plan to strip the code directly from the key in Simple Response, it needs to be done from the source application's end. You won’t be able to remove the Order ID from the keys directly in Pabbly Connect unless you capture the data in JSON format in your trigger step.

 

[JustinPM123]

@ArshilAhmad,

I used the Pabbly Text Formatter to Parse the Webhook data received and in the tests it was successful. But after saving and receiving some webhooks, the automation failed. See History ID: IjU3NjUwNTZhMDYzNTA0MzQ1MjZmNTUzNDUxMzA1MTY1NTQzMTBmMzMi_pc

After opening the Workflow to check the settings, I found the 2 new Text Format steps were not receiving data from the Webhook step. See the attached screen recording, showing that the data is showing in the Webhook step, but the following steps are missing that data.

 

[ArshilAhmad]

The tests will be successful during the workflow setup. As mentioned earlier, the issue lies with the keys changing during automation.

You need to ensure that the source application sends the correct keys.

If it’s not possible to ensure that the source application sends the same keys consistently, we can look into adding a Code step to your workflow as a workaround. However, this would require you to disable 'Simple Response' and then capture a new order in your trigger step. The response should be in JSON format.

 

[JustinPM123]

Understood. I think I have found a solution. The KEY configurations would change depending on the event_type. So I setup Routing Filters for each event_type. Then the steps within those filter workflows can consistently identify the same KEY and VALUE.

 

[JustinPM123]

That did not work. Whether I choose Simple Response or not, the data coming through on the Webhook is formatted the same. Each line is separated so I cannot capture the whole Webhook as an Array and parse out the info I need. I have attempted to use the Pabbly Code step (both JavaScript and Python) to manipulate the webhook data, but the response is always "The application processed the request but returned a blank response. Refer to the HTTP status code above for details."

Any more suggestions or ideas?

 

[ArshilAhmad]

Understood. I think I have found a solution. The KEY configurations would change depending on the event_type. So I setup Routing Filters for each event_type. Then the steps within those filter workflows can consistently identify the same KEY and VALUE.

The keys contain the order ID, which is unique for each workflow execution, so setting up a router won’t work.

That did not work. Whether I choose Simple Response or not, the data coming through on the Webhook is formatted the same. Each line is separated so I cannot capture the whole Webhook as an Array and parse out the info I need. I have attempted to use the Pabbly Code step (both JavaScript and Python) to manipulate the webhook data, but the response is always "The application processed the request but returned a blank response. Refer to the HTTP status code above for details."

Any more suggestions or ideas?

I’m afraid there are no other workarounds. We suggest getting in touch with the support team of your source application to understand how you can send consistent keys to the webhook. The keys should not include the order ID and should remain the same for all orders.