A URL you own that sona.to sends a request to when something happens, so your tools react immediately instead of checking for changes.

Which events can I subscribe to?

A post published, a post failed, a site audit completed, and a site audit failed. You pick which ones each webhook receives.

How do I know a request really came from sona.to?

Each request carries an HMAC SHA-256 signature over the timestamp and the body. Recompute it with your signing secret and compare.

What happens if my endpoint is down?

The delivery is retried after 60 seconds, 5 minutes and 30 minutes. An endpoint that keeps failing is switched off, and you can turn it back on.

Does it work with Zapier, Make and n8n?

Yes. Each of them gives you a webhook URL to paste in, and the event arrives as JSON.

Do I need the API to use webhooks?

No. You can add one from the API page in your dashboard. Managing them through the API is also possible if you prefer.

Home / Features / Webhooks

Webhooks

Send events to your tools the moment they happen

Get a signed HTTP request when a post publishes, a post fails, or a site audit finishes.

Start free today

Polling an API to find out whether something happened is wasteful and slow. Webhooks turn it around: you give sona.to a URL, and it sends a signed HTTP request the moment a post publishes, a post fails, or an audit finishes. Point it at Zapier, Make, n8n or your own server and the rest of your stack reacts on its own.

Events as they happen

Four events cover the outcomes worth reacting to: a post published, a post failed, a site audit completed, and a site audit failed. Each one carries the same fields the API returns, so a webhook and a GET agree.

Signed, so you can trust it

Every request carries an HMAC SHA-256 signature over a timestamp and the body, keyed with a secret shown once when you create the webhook. Verify it and you know the request came from sona.to and was not replayed.

Retries and a delivery log

A failed delivery is retried after 60 seconds, then 5 minutes, then 30 minutes. Every attempt is recorded with its status code and duration, so a broken endpoint is easy to diagnose rather than a mystery.

How it works

Add a URL

Paste the endpoint your tool gives you. It must use https.

Pick your events

Choose which of the four events that endpoint should receive.

Save the secret

The signing secret is shown once. Store it to verify incoming requests.

React automatically

Your workflow runs the moment something happens, with no polling.

Who it's for

Zapier, Make and n8n users triggering a workflow when a post goes out.

Teams posting publish confirmations or failures into a chat channel.