# How do you handle webhooks when you want more control over the execution layer? — retained record

> Retained reddit record from reddit:selfhosted.

Canonical: https://highsignal.app/data/records/d028390691b77fd9

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:selfhosted)  published 2026-10-21 02:03 ingested 2026-10-22 02:39

[original source ↗](https://www.reddit.com/r/selfhosted/comments/1xbasi4/how_do_you_handle_webhooks_when_you_want_more/)

## retained text



```
I've been thinking about how much control you lose when an application depends on an external service to process incoming webhooks. The setup might be convenient, but you still have to consider retries, duplicate events, API credentials, logging, and what happens when the downstream service is unavailable.

This also comes up in automated trading. TradingView Hub is one example of a cloud-based service that sits between an alert source and an exchange, which raises an interesting architectural question: how much of that workflow would you want to manage yourself?

For people who self-host their own automation tools, would you build a small webhook receiver and worker around a queue, or use an existing self-hosted workflow engine? I'd be interested to hear what you've deployed in practice and how you handle retries and duplicate requests without accidentally processing the same action twice.
```



document fetched 2026-10-22 00:32 · canonical https://reddit.com/r/selfhosted/comments/1xbasi4/how_do_you_handle_webhooks_when_you_want_more
