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

Request for Guidance on Passing Complete JSON from Webhook to Backend via Pabbly Connect

Dear Team,

I am an SAP ERP consultant, and for one of my clients, I have recommended using Pabbly Connect. The business requirement is to send WhatsApp notifications to the ERP system via an API. The messages received through the WhatsApp webhook arrive as complete JSON payloads. These need to be passed directly to the backend API without any field-level mapping.

Based on some tutorial videos, it appears that values from the webhook response must be mapped individually. However, our requirement is to forward the entire JSON payload as-is to the backend system.

Could you please advise how this can be achieved in Pabbly Connect? This is not limited to WhatsApp—similar functionality is required for other applications as well, where the goal is to send the entire incoming JSON payload to the backend without modification or mapping.

Looking forward to your support.
 

Preeti Paryani

Well-known member
Staff member
Hello @Zafar.karnalkar,

Upon checking, we noticed that you’ve already reached out to us via email, and your query is being addressed under Ticket ID: #143404.

To keep all communication and context in one place, we kindly request you to continue the discussion through the same email thread associated with this ticket.
 
Top