Zapier website monitoring with Relvato
Zapier website monitoring with Relvato connects your monitors to the apps you already use. A Zap starts the moment a monitor finds a problem, a site goes down or a vulnerability turns up, and Zaps can add sites, run monitors and set up heartbeats for you.
The Relvato Zapier app is in beta. It isn't in Zapier's public app directory yet: add it to your Zapier account with this invite link.
Connected in three steps
The app reaches your Relvato account with an API key. There's nothing to install on your site.
Accept the invite
Open the invite link, sign in to Zapier and accept it. Relvato then shows up when you choose the app for a Zap's trigger or action.
Create an API key
In Relvato, open API access and create a key. Triggers need a full-access key, and so do actions that change something, such as adding a site or running monitors.
Connect your account
In the Zap editor, choose Relvato, connect a new account and paste the key. Then pick a trigger, an action or a search.
Triggers need the Pro plan or higher and a full-access key, because they use Relvato's event subscriptions. Actions and searches work on every plan, with any key that can do the operation: a read-only key can find a site or a run, while adding sites and running monitors need full access.
9 instant triggers
Relvato sends each event to Zapier as it happens, so a Zap starts right away instead of waiting for Zapier to poll. Triggers need 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.
Trigger, action and search names are written as they appear in Zapier.
Let a Zap work in Relvato
Actions change something in your Relvato account. Searches find a site or a run for a later step to use.
Add 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 Monitor Group
Pauses one monitor group for 1 hour, for 24 hours or until you resume it, for example during maintenance.
Resume Monitor Group
Resumes a paused monitor group.
Add Heartbeat
Creates a heartbeat for a cron job or a backup and returns its ping URL and its failure URL.
Searches
Find Site
Finds a site in your account by its domain.
Find Latest Run
Finds the latest run, so a later step 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 Zap starts once per problem.
That also stops Zaps from feeding themselves. Re-running a monitor that already has a problem doesn't send the event again, so a Zap that runs monitors when one finds a problem can't trigger itself.
Triggers don't follow your Alert settings: digests, muted sites and the severity threshold are for people. Narrow what a Zap receives with the trigger's own options, such as the site and monitor groups on Monitor Found a Problem, or with a Filter step in Zapier.
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, Trello 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 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 publish
Your CMS or shop publishes a change → Run Monitors Now for one monitor group, such as the checkout flow, to see right away that it still works.
Watch a scheduled job
Add Heartbeat for a cron job or a backup. The job calls the ping URL when it finishes and the failure URL when it fails, and Relvato tells you when the pings stop.
Relvato and Zapier, answered
Why can't I find Relvato in Zapier's app directory?
The Relvato Zapier app is in beta and isn't listed in Zapier's public directory yet. Open the invite link on this page and accept it; Relvato then shows up in the Zap editor like any other app.
Which plans can use the Zapier app?
Triggers need the Pro plan or higher, because they use Relvato's event subscriptions. Actions and searches work 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. Triggers need a full-access key. Actions and searches work with any key that can do the operation: a read-only key can find a site or a run, but adding a site, running monitors or pausing a group needs full access.
Will a Zap 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 Zap starts once per problem.
Can a Zap that runs monitors trigger itself?
No. Re-running a monitor that already has a problem doesn't send the event again, so a Zap 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. Monitor Found a Problem skips those runs by default.
Do Zaps follow my Alert settings?
No. Digests, muted sites and the severity threshold are for the people you alert. A trigger gets every matching event; narrow it with the trigger's options or a Filter step in Zapier.
Can I use Zapier without the Relvato app?
Yes. A Zapier Catch Hook 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
Accept the invite, create an API key and build your first Zap, such as a Slack message when the site goes down.