A cleaner webhook setup

Hey!

We’ve reworked the webhook creation flow in the app.

Postproxy has accumulated quite a few webhook events by now: publishing updates, retry states, profile changes, comments, media failures, and more. That is useful, right up until creating a webhook starts to feel like reading a permissions matrix at 11 PM.

The new setup makes this much easier to scan.

Events are now grouped by what they relate to, so you can quickly pick what your app should actually listen for instead of working through one long undifferentiated list. Want publishing events only? Easy. Need profile connection changes? Also easy. Building around comments? Those are in their own place too.

This matters because webhooks are usually the point where Postproxy becomes part of a larger system. They let your app react immediately when something happens, for example:

• a post gets published or fails

• a retry is scheduled

• a profile disconnects

• a new comment comes in

The event model itself has not changed. We just made the configuration less annoying, which is a feature category software tends to underinvest in for mysterious reasons.

You can set up webhooks directly in the app, or read through the full reference here:
https://postproxy.dev/reference/webhooks/

If you have not used webhooks yet, they are worth a look.

Cheers,
Dmitry