Feature Requests: (1) Set HTTP headers for webhook responses & (2) Support “Return to Source / HTTP Response” mode in API module

JosChi069 · 2025-12-12T17:29:29+0530

Hello Pabbly Support Team,

I am integrating an inbound webhook from the voice assistant platform Fonio into Pabbly Connect.

Fonio requires that I return a JSON response directly to the incoming webhook request (during a live call), which means the response must include the header:

Content-Type: application/json

This is essential for Fonio to correctly parse the returned contact data.

Problem 1:

“Return Workflow Response to the Source” does not allow setting HTTP headers

In this action, I cannot define any headers at all, including the required:

Key	Value
Content-Type	application/json

Without this, the assistant cannot process the JSON correctly.

Problem 2:

The inbound webhook payload does not include a response_url

The payload Pabbly captures only shows:

fromNumber
toNumber
request headers

But no response_url, callback_url, reply_url, or similar field.

I have already contacted Fonio support to verify whether a response URL should be included. If Fonio does provide such a URL, I would be able to use API by Pabbly → Execute API Request to POST the JSON back with proper headers.

But as long as the payload in Pabbly does not expose the response_url, this is not possible.

Questions for you:

1. Is there any way in Pabbly to set Content-Type: application/json for the webhook response?

Either in

“Data Forwarder - Return Workflow Response to the Source”, or
via another action I may not be aware of.

**2. Can Pabbly expose the full raw inbound webhook body, including fields like response_url if provided by the sender?**

Currently only partial fields appear.

3. If Pabbly cannot expose a response URL or set response headers:

Would you consider adding a feature to the API by Pabbly module such as:

“Return to Source” / “HTTP Response Mode”,
allowing us to define the response headers (especially JSON Content-Type),
and return the response directly to the original webhook caller?

This would make it possible to handle integrations like Fonio that rely on webhook responses.

(As a side note: GoHighLevel has the same issue — it cannot respond to webhooks at all.
So Pabbly adding this ability would be extremely valuable for many use cases.)

Thank you very much for your help!
Please let me know if you need the full JSON payload or additional details.

Best regards,
Joachim

Hrishabh.pabbly · 2025-12-12T17:55:28+0530

Hello @JosChi069 ,

Thank you for sharing the detailed explanation — I fully understand your use case and the issue you're facing with returning data back to Fonio in JSON format.

To investigate this properly, could you please share the workflow URL where you are attempting this setup?
This will help us see how you are currently trying to send the response back.

Additionally, we may need to access your Pabbly Connect account to review the configuration.
If you're comfortable with that, please provide permission by replying with the following:

“You have my permission to log into my Pabbly Connect account and edit the workflow if required. Here is the registered email address associated with it.”

Once we receive the workflow URL and your permission, we will proceed further and assist you with the correct setup.

Looking forward to your response.

JosChi069 · 2025-12-12T18:00:22+0530

Thanks for the quick response:
Here is the Workflow URL: https://connect.pabbly.com/workflow/mapping/IjU3NjcwNTZkMDYzNTA0MzA1MjZhNTUzMzUxMzYi_pc
Workflow Execution History: https://connect.pabbly.com/task/his...=IjU3NjcwNTZkMDYzNTA0MzA1MjZhNTUzMzUxMzYi_pc#

“You have my permission to log into my Pabbly Connect account and edit the workflow if required. Here is the registered email address associated with it -> [email protected].”

ArshilAhmad · 2025-12-12T22:51:49+0530

Thank you for sharing the Workflow URL.

JosChi069 said:
Hello Pabbly Support Team,

I am integrating an inbound webhook from the voice assistant platform Fonio into Pabbly Connect.

Fonio requires that I return a JSON response directly to the incoming webhook request (during a live call), which means the response must include the header:

Content-Type: application/json

This is essential for Fonio to correctly parse the returned contact data.

Problem 1:
“Return Workflow Response to the Source” does not allow setting HTTP headers
In this action, I cannot define any headers at all, including the required:

Key Value
Content-Type application/json

Without this, the assistant cannot process the JSON correctly.

Problem 2:
The inbound webhook payload does not include a response_url
The payload Pabbly captures only shows:

fromNumber

toNumber

request headers

But no response_url, callback_url, reply_url, or similar field.

I have already contacted Fonio support to verify whether a response URL should be included. If Fonio does provide such a URL, I would be able to use API by Pabbly → Execute API Request to POST the JSON back with proper headers.

But as long as the payload in Pabbly does not expose the response_url, this is not possible.

Questions for you:
1. Is there any way in Pabbly to set Content-Type: application/json for the webhook response?
Either in

“Data Forwarder - Return Workflow Response to the Source”, or

via another action I may not be aware of.

It appears that you are using the 'Data Forwarder: Return Workflow Response to the Source' to send data back to the source, which is the correct approach.

JosChi069 said:
2. Can Pabbly expose the full raw inbound webhook body, including fields like response_url if provided by the sender?
Currently only partial fields appear.

Webhook by Pabbly is based on descriptive webhooks, which means Pabbly Connect has no control over the data that the source application sends. We simply provide a webhook URL and display the exact response received from the source application; nothing is modified or removed.

You can also connect your source application to Webhook.site (a third-party service), and you will receive the same data there as well.

JosChi069 said:
3. If Pabbly cannot expose a response URL or set response headers:
Would you consider adding a feature to the API by Pabbly module such as:

“Return to Source” / “HTTP Response Mode”,

allowing us to define the response headers (especially JSON Content-Type),

and return the response directly to the original webhook caller?

This would make it possible to handle integrations like Fonio that rely on webhook responses.

Returning the response to the source webhook URL can be handled by the 'Data Forwarder: Return Workflow Response to the Source' action step.

Thanks & Regards,
Arshil Ahmad
Customer Support Associate

Pabbly.com

Rate your support

JosChi069 · 2025-12-13T01:33:50+0530

Thank you for your reply.

So I from my understanding and for your reply it seems to me that I am not able to complete the implementation of the automation because I am not able to set the response headers which needs to be inside the action step: “Data Forwarder - Return Workflow Response to the Source”

I would need to configure the custom headers as below:

Key	Value
Content-Type	application/json

Please see also the screenshot of the Fonio instruction video about this inbound webhook response automation:

Can you please consider making this enhancement to the Action step: “Data Forwarder - Return Workflow Response to the Source”, so that we could also set status and custom headers.

Looking forward to your support.

Best regards
Joachim

ArshilAhmad · 2025-12-13T02:02:31+0530

You won't be able to set header parameters in the 'Data Forwarder' action step. If the Fonio application has an inbound webhook, you can use the API by Pabbly action step to send data to that webhook, which will allow you to include headers as well.

Thanks & Regards,
Arshil Ahmad
Customer Support Associate

Pabbly.com

Rate your support

JosChi069 · 2025-12-13T03:03:01+0530

Thank you for your reply.
As I mentioned before I dont have an API endpoint other then the response to the inbound webhook, which seems to be dynamic every time.

So at the moment it seems to me that it has to be a response to the Fonio Inbound webhook because it needs to be associated to this specific call.
If the inbound webhook would give me a response_url / callback_url I could use API by Pabbly.

But as of now this is not the case.
Fonio are working on their API documentation but it is not yet published.
I am waiting for their response on that matter.

That is why I am asking to you to forward my suggestion to add the functionality to set status and custom headers with the "Data Forwarder - Return Workflow Response to the Source” (like in Make or n8n), because to be honest I think it should have been there in the first place, because this small adjustment will make the Pabbly Connect plattform just more flexible and powerfull.

Looking forward to your support.
Best regards
Joachim

ArshilAhmad · 2025-12-13T03:14:34+0530

We have passed on your suggestion to our development team from our end. You can also post your request on our dedicated platform, where our development team can review your suggestion.

Connect: Core Feature Request | Pabbly

Vote or request new Pabbly features. Subscribe to get updates about new features from Pabbly.

roadmap.pabbly.com

Thanks & Regards,
Arshil Ahmad
Customer Support Associate

Pabbly.com

Rate your support

Feature Requests: (1) Set HTTP headers for webhook responses & (2) Support “Return to Source / HTTP Response” mode in API module

JosChi069

Member

Problem 1:

“Return Workflow Response to the Source” does not allow setting HTTP headers

Problem 2:

The inbound webhook payload does not include a response_url

Questions for you:

1. Is there any way in Pabbly to set Content-Type: application/json for the webhook response?

**2. Can Pabbly expose the full raw inbound webhook body, including fields like response_url if provided by the sender?**

3. If Pabbly cannot expose a response URL or set response headers:

Hrishabh.pabbly

Member

JosChi069

Member

ArshilAhmad

Well-known member

Problem 1:

“Return Workflow Response to the Source” does not allow setting HTTP headers

Problem 2:

The inbound webhook payload does not include a response_url

Questions for you:

1. Is there any way in Pabbly to set Content-Type: application/json for the webhook response?

**2. Can Pabbly expose the full raw inbound webhook body, including fields like response_url if provided by the sender?**

3. If Pabbly cannot expose a response URL or set response headers:

JosChi069

Member

ArshilAhmad

Well-known member

JosChi069

Member

ArshilAhmad

Well-known member

Connect: Core Feature Request | Pabbly

Similar threads

Feature Requests: (1) Set HTTP headers for webhook responses & (2) Support “Return to Source / HTTP Response” mode in API module

Member

Problem 1:​

“Return Workflow Response to the Source” does not allow setting HTTP headers​

Problem 2:​

The inbound webhook payload does not include a response_url​

Questions for you:​

1. Is there any way in Pabbly to set Content-Type: application/json for the webhook response?​

2. Can Pabbly expose the full raw inbound webhook body, including fields like response_url if provided by the sender?​

3. If Pabbly cannot expose a response URL or set response headers:​

Member

Member

Well-known member

Problem 1:​

“Return Workflow Response to the Source” does not allow setting HTTP headers​

Problem 2:​

The inbound webhook payload does not include a response_url​

Questions for you:​

1. Is there any way in Pabbly to set Content-Type: application/json for the webhook response?​

2. Can Pabbly expose the full raw inbound webhook body, including fields like response_url if provided by the sender?​

3. If Pabbly cannot expose a response URL or set response headers:​

Member

Well-known member

Member

Well-known member

Similar threads

Problem 1:

“Return Workflow Response to the Source” does not allow setting HTTP headers

Problem 2:

The inbound webhook payload does not include a response_url

Questions for you:

1. Is there any way in Pabbly to set Content-Type: application/json for the webhook response?

**2. Can Pabbly expose the full raw inbound webhook body, including fields like response_url if provided by the sender?**

3. If Pabbly cannot expose a response URL or set response headers:

Problem 1:

“Return Workflow Response to the Source” does not allow setting HTTP headers

Problem 2:

The inbound webhook payload does not include a response_url

Questions for you:

1. Is there any way in Pabbly to set Content-Type: application/json for the webhook response?

**2. Can Pabbly expose the full raw inbound webhook body, including fields like response_url if provided by the sender?**

3. If Pabbly cannot expose a response URL or set response headers: