Four ready recipes. No coding — you copy a web address, or a key, from BeOnTop into the tool you already use.
How BeOnTop talks to other tools
It tells them — in Settings, “Slack or webhook alerts” takes one web address. Every alert BeOnTop would e-mail you (a site stops answering, comes back, its score falls sharply) is also sent there, as a small message.
They ask it — in Settings you can make an API key. With it, another tool can read your sites, scores, to-dos, uptime and search words. It is read-only: nothing can be changed through it.
Recipe 1 — Any alert into any app
A site stops answering and you want a message in Slack, Teams, Gmail, WhatsApp, Trello… whatever you use.
In Zapier
In Zapier create a Zap. As the trigger choose Webhooks by Zapier → Catch Hook and copy the address it shows you.
In BeOnTop open Settings → Slack or webhook alerts, paste the address and press Connect, then Send a test.
Back in Zapier press Test trigger. You will see the test message. Now add the action you want (send a message, an e-mail, a card) and use the fields below.
In Make
In Make create a scenario. As the first module choose Webhooks → Custom webhook, add a webhook and copy its address.
Paste it into Settings → Slack or webhook alerts in BeOnTop, press Connect and Send a test.
Back in Make press Run once; the test message arrives. Add the module you want after it.
The message carries: text (the whole alert in one line), title, body, url (opens the site in BeOnTop), kind, tag, at (time) and source (“BeOnTop”).
Recipe 2 — Every site’s score in a spreadsheet, each week
A Google Sheet that grows by one row per site per week — a free history you can chart.
In Zapier
In BeOnTop open Settings → API keys, make a key, and copy it (it is shown once).
In Zapier: trigger Schedule by Zapier → Every Week. Action Webhooks by Zapier → Custom Request: method GET, address https://beontop.app/api/v1/sites, header Authorization with the value Bearer + a space + your key.
Add Looping by Zapier over the sites list, then Google Sheets → Create Spreadsheet Row with host, score, openTodos and lastCheckedAt.
In Make
Make an API key in BeOnTop as above.
In Make: Schedule (weekly) → HTTP → Make a request: GET https://beontop.app/api/v1/sites, header Authorization: Bearer your-key, parse the answer as JSON.
Add Iterator on sites, then Google Sheets → Add a Row with host, score, openTodos, lastCheckedAt.
One request gets all your sites (competitors are not included). A key may make 1000 requests a day.
Recipe 3 — Tell me when a score is low
Build on Recipe 2: only act on sites whose score is below a number you choose.
In Zapier
In the Zap from Recipe 2, after the Loop add Filter by Zapier: continue only if score is less than, say, 70.
Then add the action: a Slack message, an e-mail to yourself, a Trello card.
In Make
In the scenario from Recipe 2, click the line between Iterator and the sheet and add a filter: score less than 70.
Put the module you want (Slack, Gmail, Trello…) after it.
A site that has not been checked yet has no score, so the filter skips it.
Recipe 4 — Open fixes become tasks
Each to-do BeOnTop finds becomes a card in Trello, Asana, Todoist or any task list.
In Zapier
Use the key from Recipe 2. First get the site’s id from https://beontop.app/api/v1/sites (the id field).
In Zapier: trigger Schedule, action Webhooks → Custom Request: GET https://beontop.app/api/v1/sites/{id}/todos?lang=en with the same header, then Looping over the open list and a Create Task / Card action.
In Make
Same key. In Make: Schedule → HTTP → Make a request to https://beontop.app/api/v1/sites/{id}/todos?lang=en, parse JSON, Iterator on open, then the task module.
Use lang=el for Greek text. To avoid the same task twice, search for it in your task tool first, or only create it once a week.
Good to know
The webhook takes one address per account, https only. BeOnTop tries once per alert and pauses after 20 failures in a row — save the address again to resume.
The address and the API key are secrets: anyone who has one can use it. If a key leaks, revoke it in Settings and make a new one.
Menu names in Zapier and Make change now and then; the idea of each step stays the same.
These recipes use the standard Zapier and Make modules. We have written them from their documentation and BeOnTop’s own behaviour; if a step looks different on your screen, tell us at info@aqua4all.org.