want to send limited data in webhook

Status: Open · Asked by Parth Nayak on · 0 views

Preeti Paryani — Reply ·

Hi @Parth,

To send only limited data in your webhook, you can use the Data Forwarder (Pabbly) action.

Select the action event “Forward Custom Data”, and then manually create only those parameters (keys) that you want to send. Map the required 4 fields there, and only those will be forwarded in the webhook payload (in JSON format).

This way, even if you receive 15 data points, only the selected ones will be sent further.

For better understanding, please refer to the tutorial you shared — it explains the setup clearly.

youtube.com/watch?v=JwjWx7vx0hE:360

Let us know if you face any issues while configuring it.

Parth Nayak — Reply ·

we have tried sending details but end user is facing issue

Preeti Paryani — Reply ·

Hey @Parth,

It seems you're trying to send data to a third-party webhook.

Please note that the Data Forwarder (Pabbly) action is primarily used to send data to another Pabbly workflow. For sending data to an external/third-party application, we recommend using the API (Pabbly) module instead.

There, you can structure your JSON body and include only the specific fields (e.g., 4 data points) that you want to pass.

Let us know if you need help setting up the API step.

Parth Nayak — Reply ·

how to do that step by step, can you guide

Preeti Paryani — Reply ·

Hey @Parth,

It appears that you have successfully configured the API (Pabbly) action in your workflow, and it seems to be functioning correctly. Can you please confirm if the issue has been resolved or if you need any further assistance?

Arshil Ahmad — Reply ·

If you want to trigger the webhook without sending any data, then yes, step 2 of your workflow, “API (Pabbly),” has been set up correctly.

Thanks & Regards,
Arshil Ahmad
Customer Support Associate
? Pabbly.com
?Rate your support

drgeetha — Reply ·

Hi @Parth,

The current setup looks correct.

Using the API module in Pabbly Connect is the right approach when sending limited data to an external webhook. Instead of forwarding all 15 fields, you can define a custom JSON body and include only the required 4 data points.

This ensures:

  • Clean payload structure
  • No unnecessary data sent
  • Better compatibility with third-party systems

Your updated workflow configuration appears properly aligned with this method.

crystalengineers — Reply ·

Hi @Parth,

Yes, your updated setup looks correct ?

Using the API (Pabbly) module is the right way when sending limited data to a third-party webhook. Instead of forwarding all 15 fields, you just need to create a custom JSON body and include only the 4 required data points.

This helps in keeping the payload clean and avoids unnecessary data being sent.

If your webhook is still facing issues, you may want to double-check:

  • Field mapping
  • JSON format
  • Required parameters from the receiver side

Back to all forum threads · Log in to reply