🔗 Webhooks

Would love this feature - being able to setup headless automations, would be great. Especially with background work-tasks and full featured code that can run. We might want to use this kind of a feature with a wordpress plugin front-end, to take a submission, run a long - running process with it, then when it's "finished", it will ping-back to the front-end and say hey, your results are ready... Our example use case may be: get a request to write an article, or a custom study guide with what the student should really focus on (because they missed specific things in a set of quizzes for example), then prepare the docx or pdf, on a background process, and ping the front end when it's ready for delivery.

Voting for this. Concrete need from my side: I want to accept inbound webhooks on my custom /x/* routes, but today those require the platform's edge token, which third-party services can't obtain. A per-route custom auth option would unlock this: a static bearer token or API key that I generate and share with the webhook sender (e.g. iOS Shortcuts automation, or any SaaS that has no Vellum integration yet). Even a simple per-route auth config like `auth: { type: "static-token" }` in the route file, with the secret stored in the assistant's credential vault, would cover most cases. Later, HMAC signature verification would be a natural follow-up.