A webhook is the simplest way to connect anything to anything: one service makes an HTTP request to a URL, and another service reacts. With Noria you get a unique webhook URL for each workflow, so any app that can send a webhook can kick off a no-code automation — no polling, no server, no code.
How it works
- Add a Webhook trigger. Noria generates a unique URL for that workflow.
- Point a service at it. Paste the URL into anything that sends outgoing webhooks — a form builder, a payment provider, a monitoring tool, a CI pipeline, or your own backend.
- Use the payload. Whatever JSON the service POSTs is available to every downstream node as variables.
- Add actions. Call an API, send an email, post to Discord, branch on a condition — whatever the event should do.
- Activate. From now on, every request to the URL runs your workflow.
Reading the incoming data
The body of the request is exposed through template variables. If a form tool POSTs { "email": "[email protected]", "plan": "pro" }, you can reference it anywhere:
{{__trigger__.body.email}}
{{__trigger__.body.plan}}
{{__trigger__.headers.x-signature}}
The expression field autocompletes the available paths and flags typos before you ship — see triggers and actions for the full variable model.
Examples
- New signup → welcome flow. A form submission hits your webhook → send a welcome email → post
New signup: {{__trigger__.body.email}}to a Discord channel. - Payment received → fulfilment. A payment provider's webhook → an HTTP request to your fulfilment API → a confirmation email.
- Monitoring alert → on-call ping. An uptime monitor POSTs an incident → a Condition checks the severity → a Discord or email alert goes out only for criticals.
- App event → data sync. Your own backend posts an event → transform it → push it to another API with the HTTP request action.
Securing your webhook
- Keep the URL private. Each workflow's URL is unique — anyone who has it can trigger the workflow, so share it only with the service that needs it.
- Verify a shared secret. Have the sender include a secret token (in the body or a header), then add a Filter or Condition node at the top of the workflow that ends the run unless the token matches. This blocks anyone who stumbles onto the URL.
- Validate the shape. Add a condition that checks the fields you expect exist before doing anything irreversible.
Next steps
- Pair webhooks with scheduled automation for jobs that run both on demand and on a timer.
- Push the result to Discord or any REST API.
- Browse templates for ready-made webhook flows, or create a free account and build your own in minutes.