Add custom response for webhook

Feature Requests
1

What’s the feature?

  • Currently, webhook systems typically only return default responses.
  • In many cases, users want to create notifications, logs, or trigger additional actions based on the webhook response content.
  • Supporting custom responses makes the system more flexible and easier to integrate with various external services or more complex business logic.

Your use case

The webhook receiver can receive appropriate responses without needing to modify the webhook caller.

  • Support for workflows/log analysis: Resend detailed messages to facilitate monitoring and error handling.
  • Expand integration capabilities: Custom responses enable more effective and flexible integration with external systems.
3

Hi,

Thanks for the detailed explanation — the use case is clear.

What you’re describing is synchronous webhook processing — keeping the HTTP connection open while the automation runs and returning the result inline. The reason the industry moved away from this is that automation processing time is unpredictable, and holding a connection open that long leads to timeouts and dropped requests. That’s why platforms like Stripe, GitHub, and Slack all use the same async model.

The standard pattern for your use case is: webhook triggers the automation → automation processes the data → POSTs the result back to your endpoint when complete. One extra step, but it’s the approach that holds up reliably in production.