Webhooks
Get notified the instant something happens in Autousers — no polling, no scripts.
What are webhooks?
Instead of opening Autousers every few minutes to check whether your evaluation is done, webhooks let Autousers tell you — instantly — the moment something happens. Think of it like a delivery notification on your phone: you do not have to keep checking the tracking page, the courier pings you when the parcel arrives.
When something happens in your team — an evaluation completes, a teammate submits ratings, an autouser finishes — Autousers sends a small message to a URL you choose. That URL can be a Slack channel, a Linear inbox, a spreadsheet, or anything in between.
When should I use webhooks?
Webhooks shine when you want something to happen automatically the moment an Autousers event fires. A few real examples:
- Slack alerts — Get a message in your team channel the second a teammate finishes their human ratings, so you can review results without refreshing the dashboard.
- Linear tickets — Automatically create a Linear issue when an evaluation scores below 70% on Usability, so the design team has a follow-up waiting in their queue.
- Looker / BigQuery dashboards — Pipe every rating into your warehouse so weekly research data lands alongside the rest of your product metrics.
- Notion or Airtable logs — Append a row to a research log every time an evaluation is created, with no copy-paste required.
No engineers handy? No-code routers like Zapier, Make.com, n8n, and Pipedream all accept webhooks. They give you a URL, you paste it into Autousers, and they handle fanning the event out to Slack, Notion, Sheets, Linear, or any of the hundreds of apps they integrate with.
What events fire?
Autousers sends webhooks for seven events. Subscribe to all of them or pick only the ones you care about.
- evaluation.created — A new evaluation is created.
- evaluation.status_changed — An evaluation moves between Draft, Running, and Ended.
- evaluation.completed — All ratings are in and the evaluation is closed.
- autouser_run.completed — An AI persona finishes evaluating one design.
- autouser_run.failed — An AI persona run errored out and could not finish.
- rating.created — Anyone (a human teammate or an AI persona) submits a rating.
- calibration.frozen — A new calibrated persona version is locked in.
How do I set one up?
- Open Settings → Webhooks at /settings/webhooks.
- Click Create endpoint.
- Paste the URL of your receiving service — webhook.site for a quick test, your Zapier or Make hook URL, or your own server endpoint.
- Pick which events you want. Not sure? Leave All events ticked — you can narrow it later.
- Copy the signing secret. It is shown once and proves to your receiver that the message really came from Autousers.
- Click Send test event and watch a successful delivery appear in the Deliveries log within seconds.
Do I need to be a developer?
Not really. Posting webhooks to your own server does need an engineer to write a small handler that verifies the signature — that side lives in our engineer-facing docs at https://docs.autousers.ai/webhooks.
For everyone else — designers, PMs, design-ops, research leads — the easiest path is a no-code router. In Zapier, create a new zap with Webhooks by Zapier → Catch Hook as the trigger, copy the URL Zapier gives you, and paste it into Autousers. Then pick the action: Slack message, Notion page, Google Sheets row, Linear issue. Make.com, n8n, and Pipedream all work the same way — five minutes, no code.
What plan do I need?
Webhooks are included on the Pro plan ($299/mo) and Enterprise. Free, Indie, and Team accounts can read this article and explore the dashboard, but cannot create endpoints. To upgrade, head to /pricing.
FAQ
What if my receiver is down?
We retry. If your endpoint returns an error or times out, Autousers automatically tries again with exponential backoff for about three days before marking the delivery failed. You can replay any failed delivery manually from the Deliveries log.
Can I see what was sent?
Yes. Every endpoint has a Deliveries tab showing the last 30 days of attempts — what was sent, what your receiver returned, and how long it took. First place to look if something is not arriving.
Is the data secure?
Every payload is signed with the secret we showed you when you created the endpoint. Your receiver should verify that signature on every request in production — it is what stops anyone else pretending to be us. The how-to lives at https://docs.autousers.ai/webhooks for the engineer setting up your handler.
Can I have multiple endpoints?
Yes — most teams do. A common pattern is one endpoint pointing at Slack for human alerts, and another pointing at your warehouse for the long-term log. Each endpoint has its own URL, event subscriptions, and signing secret.
How do I stop them?
Open the endpoint in Settings → Webhooks and toggle it to Disabled — the endpoint stays in your list but no events go out. To remove it entirely, click Delete. Deletion is permanent: the deliveries log goes with it, so disable first if you might want it back.