Webhooks in Unstructured Pipelines: our quick take. How about yours?

We’ve been talking lately about webhooks in Unstructured Pipelines (posts 1, 2). You can read more about it here.

Honestly, the core mechanism is simple by design. And that's mostly a good thing. Five job states, JSON payloads, and your receiver does the rest. Nothing exotic to learn, which means it's been quick for people to adopt.

One thing to note: deleting webhooks is permanent. There's no undo, no soft-delete, no recovery window. If a webhook is wired into something important, double-check before you remove it. 

Oh, and another: we know workflow-scoped webhooks currently exist in the API but not yet in the UI. If you want a no-code approach for workflow-scoped webhooks right now, sorry; you have to go through the API.

What's your take? Does that match your experience setting one up, or did you hit something we haven't mentioned?