• Instructions to Ask a Question

    For any assistance, please click the "Ask a Question" button and select the Pabbly product for which you require support.

    We offer seven comprehensive applications designed to help you efficiently manage and grow your business:

    Our support team endeavors to respond within 24 business hours (Monday to Friday, 10:00 AM to 6:00 PM IST). We appreciate your understanding and patience.

    🚀 Exclusive Lifetime Offers 🚀

    We invite you to take advantage of our special one-time payment plans, providing lifetime access to select applications:

    • 🔥 Pabbly Connect — Lifetime Access for $249View Offer
    • 🔥 Pabbly Subscription Billing — Lifetime Access for $249View Offer
    • 🔥 Pabbly Chatflow — Lifetime Access for $249View Offer

    Make a one-time investment and enjoy the advantages of robust business management tools for years to come.

workflow will not map responses properly and response contains the pair in the value field

Durkis

Member
I am buildubg a group of auomations. today the transfer of data between flows in APIS to webhooks started to pass the value/key pair in the value field so that every transfer adds a new key feild. I have noticed this before. How do I get around this?
I am also seeing values slip back to ummapped absolute values.
this test series of flows is the second try.

 

Attachments

  • 1740146436234.png
    1740146436234.png
    153 KB · Views: 69
  • 1740146526619.png
    1740146526619.png
    145.1 KB · Views: 63
  • 1740146631288.png
    1740146631288.png
    137 KB · Views: 67

ArshilAhmad

Moderator
Staff member
Hi @Durkis,

Could you please record a short screen recording showing the exact issue you’re encountering? This will allow us to gain a better understanding of your issue.
 

Durkis

Member
It seems there is a problem with dymanic mapping. I am building a series of automations linked via Pabbly API step/ webhook step. I have found that instead of passing along the dynamically mapped key/value pair in the usual way, the workflows sudddenly started to pass the key field as written , and key : value in the value field, seemingly reading it as a non dynamic, literal value. this happened all of a sudden, and I cant find a map button in the usual place to fix this.

as I go form the second workflow to the third through another API to webhook connection, the same thing happens, compounding the problem: Key in the Key feild and Key : Key: : value in the value feild. Seethe screen captures above.

I have his this issue before and the only way I could deal with it was to re create teh flow, but these are complex and important wrokflows! (the shared example is my second try to see if that solved this issue) any suggestion?is this a bug?
 
Top