Webhooks for Unstructured Pipelines are now live. Here's why we built it.

For a long time, the only way to know what was happening with an Unstructured processing job was to keep refreshing a dashboard or write your own polling script against the Unstructured API. That's fine if you're babysitting one job, but it falls apart the moment you've got pipelines running unattended. Failures sit there until someone happens to check, and successful runs don't trigger anything downstream without extra glue code.

We kept hearing the same pattern from people running Unstructured Pipelines at any real scale: they wanted to know the moment something failed, not five minutes (or five hours) later when someone happened to look. And they wanted that signal to actually do something, like page an on-call engineer, kick off a CI step, or drop a message in Slack. And they didn’t want to have to stand up their own polling infrastructure just to bridge that gap.

That's why webhooks for Unstructured Pipelines are live now. You can register a receiver URL and get notified the instant a job hits a state you care about: scheduled, in progress, stopped, failed, and completed. The payload is JSON, the setup takes a few minutes, and it plugs into whatever you're already using on the other end. Lambda, a Cloud Run function, Zapier, Slack, or just an endpoint you stood up yourself. Docs are up if you want to wire one in today…get the details here.

Does this resonate with you? Is "I find out about failures too late" a pain point you've actually hit, or has polling been good enough for your setup?