What webhooks in Unstructured Pipelines unlocks for you…your thoughts?

We just kicked off a discussion a few days ago about our webhooks. Let’s talk more about why it matters.

The obvious one is alerting: you can route a failed-job event straight to your on-call rotation instead of someone noticing a stale dashboard. But the more interesting unlock is treating job completion as a trigger for actual work, not just a status you check.

A completed event can kick off a downstream sync, fire a CI/CD step, or hand off to whatever automated process is waiting on fresh data. A failed event can do more than alert. It can roll back a deploy, retry with different parameters, or flag a record for human review. Because the payload goes to a receiver URL, you're not locked into any one integration; it's worked through AWS Lambda, Azure Functions, Google Cloud Run, Zapier, Slack, Svix, and plain webhook testing tools, so whatever's already in your stack is probably already supported.

Oh, and something from a security perspective. You can sign your webhook with a secret so the receiving side can verify the request actually came from us and wasn't spoofed. Use this technique if your endpoint triggers anything sensitive.

Here are the docs, if you want to learn more.

What do you think? Any interesting projects you'd reach for this with? Something you'd actually wire a webhook into rather than just checking a dashboard for?