refactor(nodes-base): return response body on RespondToWebhook

[ndeitch]

Summary

Returns body, statusCode & headers in RespondToWebbhook node.

This is useful to have access to workflow response in postExecute workflows hooks.

Review / Merge checklist

• PR title and summary are descriptive. (conventions)
• Docs updated or follow-up ticket created.
• Tests included.
• PR Labeled with release/backport (if the PR is an urgent fix that needs to be backported)

Test Proof

[Joffcom]

Hey @ndeitch

This goes against how the node works and our general design approach, it is meant to return only the input data rather than what gets sent back to the webhook.

I can't see what benefit this actually has at the moment as the body data can be accessed from node parameters.

Do you have some examples on how this would actually be used?

[ndeitch]

Hi @Joffcom, thanks for the quick review!

I see your point and indeed I can do it without this change. I did this because I have a backend hooks of type workflow.postExecute that checks the result of each execution and saves it in an external database.

Returning the response in the node makes it easier to save the workflow execution result, otherwise I need to check the result of each node used to build the response to get to the result returned by RespondToWebhook node.

[Joffcom]

Hey @ndeitch,

It sounds like if you are using n8n embed and hooks maybe a fork that includes this one change could be a possible route as I am not sure if this would benefit other users. This did come up on the forum recently though and I did come up with a possible solution which involved multiple output branches like the image below would that sort of approach work for you?

[ndeitch]

Hey @ndeitch,

It sounds like if you are using n8n embed and hooks maybe a fork that includes this one change could be a possible route as I am not sure if this would benefit other users. This did come up on the forum recently though and I did come up with a possible solution which involved multiple output branches like the image below would that sort of approach work for you?

Alright, I'll create my own RespondToWebhook node then. Thanks!