Make website monitoring with Relvato
Make website monitoring with Relvato connects your monitors to the apps you already use. A scenario starts the moment a monitor finds a problem, a site goes down or a vulnerability turns up, and scenarios can add sites, run monitors and set up heartbeats for you.
The Relvato Make app is in beta. It isn't in Make's app directory yet: install it in your Make organization with this invite link, then search "Relvato" when you add a module to a scenario.
Connected in three steps
The app reaches your Relvato account with an API key. There's nothing to install on your site.
Install the app
Open the invite link and install the Relvato app in your Make organization. It isn't in Make's app directory yet, so this is how you add it until that review finishes.
Create an API key
In Relvato, open API access and create a key. Watch events needs a full-access key, and so does any action that changes something, such as adding a site or running monitors.
Connect your account
In a scenario, search for Relvato when you add a module, connect a new account and paste the key. Then pick Watch events, an action or a search.
Watch events needs the Pro plan or higher and a full-access key, because it uses Relvato's event subscriptions. Every other module works on every plan, with any key that can do the operation: a read-only key can list sites or get a run, while adding sites, running monitors and the other actions need full access.
9 trigger events
Relvato sends each event to Make as it happens, so a scenario starts right away instead of waiting for Make to poll. Watch events needs the Pro plan or higher.
Monitor Found a Problem
A monitor went from passing to finding a problem. Choose the site and the monitor groups. By default it skips runs that couldn't happen, such as a firewall block or the site not answering.
Monitor Recovered
A monitor that had found a problem passes again.
Site Down
Uptime monitoring finds the site down.
Site Back Up
The site answers again after being down.
New Vulnerability Found
A vulnerability monitor finds a known vulnerability on the site: on WordPress, and on Drupal, Joomla, PrestaShop and Magento sites too.
Page Looks Different
Visual regression monitoring finds a page that looks different from its approved baseline.
Search Traffic Dropped
The site's search traffic dropped, as measured from Google Search Console or Bing.
SSL Certificate or Domain Expiring
The site's SSL certificate or its domain registration is close to expiring.
Quarantine Mode Change
Quarantine mode noticed changes on a site that was just cleaned after a hack.
Module names are written as they appear in Make.
Let a scenario work in Relvato
Actions change something in your Relvato account. Searches find a site or a run for a later module to use.
Add a site
Adds a website to Relvato. If the site is already there, you get the existing one back instead of a duplicate.
Start monitoring for goals
Adds the monitors that match the goals you choose for a site.
Run monitors now
Runs a site's monitors now: all of them, or one monitor group. Each run counts toward your plan's monthly runs.
Pause a monitor group
Pauses one monitor group for 1 hour, for 24 hours or until you resume it, for example during maintenance.
Resume a monitor group
Resumes a paused monitor group.
Add a heartbeat
Creates a heartbeat for a cron job or a backup and returns its ping URL and its failure URL.
Get a site overview
Returns Relvato's plain-language verdict for a site: what's working, what needs attention and why.
Make an API call
Calls any Relvato REST API endpoint with your connection, for anything the modules above don't cover.
Searches
List sites
Lists the sites in your account.
Get the latest run
Gets a site's latest run, so a later module can use its result.
On a change, not on every run
Relvato sends an event when a monitor changes state: from passing to finding a problem, or from a problem back to passing. A monitor that keeps finding the same problem doesn't send the event again on each run, so a scenario starts once per problem.
That also stops a scenario from feeding itself. Re-running a monitor that already has a problem doesn't send the event again, so a scenario that runs monitors when one finds a problem can't trigger itself.
Watch events doesn't follow your Alert settings: digests, muted sites and the severity threshold are for people. Narrow what a scenario receives with the trigger's own site and monitor-group filters, or with a Filter in Make.
Make registers the event subscription with Relvato when you turn the scenario on, and removes it when you turn it off or it stops — so the subscription only exists while the scenario that watches for it is running.
What you can build with it
Tell the on-call person the site is down
Site Down → an SMS, or a message in a Slack channel. Add Site Back Up to send the all-clear when it answers again.
A ticket for every vulnerability
New Vulnerability Found → an issue in Jira or Linear with the site and the run link, so the update gets planned.
An incident log in a spreadsheet
Monitor Found a Problem → a new row in Google Sheets for each problem, with the site, the monitor and the time.
Agency onboarding from a sheet
A new row in a sheet → Add a site, then Start monitoring for goals. Each client site gets the monitors for its goals; they run on schedule once the site's ownership is proven.
Re-run monitors after a deploy
Your deploy webhook → Run monitors now for one monitor group, such as the checkout flow, to see right away that it still works.
A weekly site-health digest
A weekly schedule → Get a site overview for each site, collected into one email with Relvato's plain-language verdict for every client.
Relvato and Make, answered
Why can't I find Relvato in Make's app directory?
The Relvato Make app is in beta and isn't listed in Make's public app directory yet — Make reviews an app before listing it. Open the invite link on this page, install the app in your Make organization, and search "Relvato" the next time you add a module to a scenario.
Which plans can use the Make app?
Watch events needs the Pro plan or higher, because it uses Relvato's event subscriptions. Every action and search works on every plan, Free included. Run monitors now counts each run toward your plan's monthly runs.
Which API key do I need?
Create one under API access in Relvato. Watch events needs a full-access key. Actions and searches work with any key that can do the operation: a read-only key can list sites or get a run, but adding a site, running monitors or pausing a group needs full access.
Will a scenario start on every run that finds a problem?
No. Relvato sends an event when a monitor changes state, from passing to finding a problem or back to passing. A monitor that keeps finding the same problem doesn't send it again, so a scenario starts once per problem.
Can a scenario that runs monitors trigger itself?
No. Re-running a monitor that already has a problem doesn't send the event again, so a scenario that runs monitors when one finds a problem can't start a loop.
What about runs that couldn't happen?
When a firewall blocked Relvato or the site didn't answer, the run couldn't happen and says nothing about what's on your site. Watch events skips those runs by default.
Does Watch events follow my Alert settings?
No. Digests, muted sites and the severity threshold are for the people you alert. Watch events gets every matching event; narrow it with its own filters or a Filter in Make.
Can I use Make without the Relvato app?
Yes. A Make Custom webhook module accepts Relvato's webhook as it is, and the REST API lets any tool subscribe to events. The app does the subscribing for you and adds the actions and searches.
More ways to work with Relvato
Put your monitors to work in your other apps
Install the app, create an API key and build your first scenario, such as a Slack message when the site goes down.