A webhook reverses the usual direction: instead of another program asking snori "is there anything new?", snori speaks up by itself the moment something happens. That turns your workspace into an active source – events flow out in real time to the tools waiting for them.
What is a webhook?
A webhook is an automatic machine-to-machine notification. You store a target address (a URL), and whenever a certain event occurs, snori sends a small record to exactly that address. The format is usually JSON and contains what just happened – for example which row was created and in which table.
The difference to classic polling is decisive. Without a webhook, another program would have to ask snori every few seconds whether there is anything new – which costs time and resources and is still always a little too late. With a webhook that asking disappears entirely: snori speaks the moment it has something to say. That is why webhooks are the standard for firing automations exactly when the trigger really occurs. Because they are part of the interface, webhooks cost nothing extra with snori.
snori and webhooks: the direction
Webhooks make snori the source. The event arises in your workspace, and the notification goes out.
snori as the source – snori reports what happens
You create a new page, a new row appears in a smart table, an entry changes: snori immediately sends a message to the address you stored. Behind it there can be an automation service that then sends an email, posts to Slack or updates a record in a CRM. snori is the starting point, your next tool takes over.
snori as the target – the other way round
If data should instead flow into snori, the webhook is not the way – the Workspace API is: another system then actively writes into your workspace. Webhook (out) and API (in) complement each other – together they cover both directions.
How to set up the connection
- In snori, open the settings for the Workspace API and create an access key for this workspace.
- You store the target address (URL) that snori should report events to.
- You choose which events trigger a notification – for example only new rows, or changes as well.
- Done: from the next matching event on, snori sends its message out in real time.
No server on your side has to keep asking – the notification arrives by itself as soon as there is something.
Who can access your data
Even when actively reporting, snori stays sparing. A webhook notification contains only what the event requires, and goes solely to the address you entered yourself. The associated key carries exactly the rights you set and applies to one workspace only. If you want to stop the reporting, you deactivate the webhook or revoke the key – it ends at once. Every process is versioned, and your content stays encrypted in a German data centre certified to ISO 27001.
Webhook, API or AI – when to use what?
A webhook is ideal when snori should kick something off the moment it happens – the push outward. If you instead want to actively query data from snori or write into it, you use the Workspace API. Without your own code, the easiest way to catch webhook notifications is an automation service like Zapier, which receives the message and processes it further. If an AI should access your workspace, the AI connection is the right way.