• 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.

Salesforce response not being parsed correctly

nsdev

Member
Since yesterday, Pabbly is not correctly parsing the response from Salesforce and this causes the workflow to not move forward.
We already tested the Lead generation via Postman and the response from Salesforce is correct.

Scenario:
We're sending lead via Gravity Forms to Salesforce.
Once the Lead is created, we add a delay and then try to update a field on the Lead.
But since Pabbly is not parsing the response correctly, then no Lead ID is captured and so the update also fails and breaks the workflow.

Task ID: IjU3NjUwNTZiMDYzNDA0MzA1MjZhNTUzNzUxMzE1MTYzNTQzNTBmMzMi_pc

1756834758377.png
 

Preeti Paryani

Well-known member
Staff member
Hello @nsdev,

It seems the record creation request is reaching Salesforce, but the response is not returned within Pabbly’s 25-second capture window. Postman waits up to 30 seconds, which is why it worked fine there. Please try re-executing a task history to see if it works now. If the issue continues, kindly share a screen recording of the test in both Pabbly and Postman. Do note, if Salesforce does not respond within 25 seconds, this needs to be addressed at the API end.
 
Top