Webhooks

Make, Zapier, n8n

How to receive AOA webhooks without your own server: connecting Make, Zapier and n8n step by step, registering the URL in AOA and the most common scenarios.

You don’t have to write a server to receive our webhooks. Automation builders can catch HTTP requests out of the box: you get a URL from them, register it in AOA, and then build the scenario with your mouse.

There’s no separate AOA app in their catalogs

You connect through the generic webhook module that each of these services has. It’s the standard way, not a workaround: most integrations between smaller platforms work like this.

Make

Our default pick for a small team: receiving webhooks is available even on the free plan.

Create a scenario and add Webhooks > Custom webhook as the first module.
Click Add, give it a name and copy the URL Make gives you.
Register that URL in AOA (command below).
Go back to Make: it waits for the first request to learn the data structure. Pay for a test ticket or wait for a real event, and the fields will appear on their own.
Then add whatever you need: a row in Google Sheets, a Telegram message, a card in your CRM.

Zapier

Create a Zap and pick the Webhooks by Zapier > Catch Hook trigger.
Copy the URL Zapier gives you.
Register it in AOA.
Click “Test trigger” and wait for the first event.

A paid plan is required

Webhooks by Zapier is a premium module and isn’t available on the free Zapier plan. If the plan doesn’t matter to you and you only need to receive webhooks, Make will cost less.

n8n

A good fit if you want to keep data on your side: n8n can run on your own server.

Add a Webhook node with the POST method.
Copy the Production URL and register it in AOA.
You can verify the signature with a Code node: there’s an example on the “Verifying signatures” page.

Registering the URL

This step is the same for all three services. Put in the URL you got:

cURL

curl -X POST https://aoa.com.ua/api/v1/webhooks \
  -H "Authorization: Bearer aoa_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "PASTE_YOUR_MAKE_URL_HERE",
    "events": ["order.paid"]
  }'

No terminal at hand? Send us the URL and the list of events, and we’ll register it for you.

What people build most often

Scenario	Event	Why
Every sale as a row in Google Sheets	`order.paid`	Your own reporting in a familiar spreadsheet
A notification in the team chat	`order.paid`	The team sees sales in real time
The buyer’s contact in your CRM	`order.paid`	The customer base fills itself
A cancellation alert	`event.cancelled`	Time to warn those who have already bought
Refund reconciliation	`order.refunded`	Accounting sees refunds without manual exports

Builders usually skip signature verification, since the webhook URL there is long and random. If personal data goes through it, it’s still better to verify: in Make that’s a Code node, in Zapier a Code by Zapier step.