OffAlerts Zapier integrationAutomate OffAlerts with Zapier.
The OffAlerts Zapier integration gives you 1 trigger and 0 actions. Each new event logged by your OffAlerts uptime monitors can start a Zap that opens a ticket, posts to a channel or fills an incident log. Here is how it fires, what it costs and why timing matters.
Verified Trustpilot reviews · AI, automation & growth agency
What the OffAlerts Zapier integration actually does
OffAlerts watches your websites and apps with uptime monitors, runs status pages, and alerts you by email, SMS or push when something goes offline. Connecting it to Zapier lets each monitor event travel further: into the tools where your team tracks incidents, talks to customers or keeps a record of what happened.
Everything starts from New Monitor Event, and the value comes from where you send it. Three results are typical. An incident log that fills itself: each event adds a row to a shared sheet, and the monthly review of outages no longer depends on someone remembering them. A ticket for every event: your help desk or project tool gets a card, so a follow-up is assigned instead of lost in an inbox. A message in the team channel: the people who are not on OffAlerts' own notification list still see that a monitor fired.
Now the limits, and one matters more than the rest. The trigger works by polling: Zapier checks OffAlerts on a timer, every 15 minutes on the free plan. OffAlerts' own email, SMS and push alerts stay your first line; the Zap is a second, slower channel for logging and follow-up. There are no actions either, so a Zap cannot pause a monitor or update a status page, and there is no search to look up a past event.
Choosing between platforms? The n8n vs Zapier and Make vs Zapier comparisons list the criteria (pricing model, hosting, step limits) without naming a winner.
Zapier vocabulary in one minute
Seven words are enough for the rest of this page. Each is explained here once, then used as is.
- Zap
- The automation you build: one trigger, then one or more actions that run every time that trigger event happens.
- Trigger
- The event that starts the Zap, here a new OffAlerts monitor event. Once the Zap is on, Zapier keeps watching for it.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something for you in another app.
- Task
- The unit Zapier bills. One task is one action that completes successfully; plan quotas are counted in tasks.
- Polling vs instant
- Polling means Zapier checks an app on a timer for new items. Instant means the app calls Zapier itself when something happens.
- Filter
- A step that lets the Zap carry on only when the incoming data meets the condition you set, and stops it otherwise.
- Search step
- A step that finds something already stored in an app so later steps can use it. OffAlerts has none on Zapier.
What it really costs in tasks
OffAlerts is not a premium app, so it works on the free Zapier plan. You pay in tasks, and the OffAlerts trigger never uses one.
- Free plan100 tasks per month
- Steps per Zap on Free2: one trigger, one action
- Premium appNo
- OffAlerts trigger typePolling
Neither the trigger nor the checks Zapier runs to spot new events cost anything, however often they happen. Only the action that follows counts, one task per success; a failed action is not counted. A Zap with three actions uses three times what a one-action Zap uses. The free plan gives you 100 tasks a month and unlimited Zaps, but two steps per Zap and a check every 15 minutes. A filter (only events from your main site, say) or a second action makes the Zap multi-step, which needs a paid plan. For alerts, the faster checks of paid plans in the grid below matter as much as the task count.
Connect your OffAlerts account
- 01
Open your connections
In Zapier, go to the Apps page of your account and click + Add connection. A connection is your OffAlerts account linked once, then reused by every Zap step that touches OffAlerts.
- 02
Pick OffAlerts
Search for OffAlerts in the dialog, select it and click Add connection. A tab opens on the OffAlerts side. You need an OffAlerts account that can see the monitors whose events you want.
- 03
Sign in and grant access
Log in to OffAlerts in that tab and let Zapier reach your account. When the tab closes, the connection shows in your list and the OffAlerts trigger in any Zap can use it.
Your first Zap: log every monitor event
GoalEach new OffAlerts monitor event becomes a row in an incident log, with a ticket for the follow-up.
- 01
Create the Zap
In the Zapier editor, start a brand new Zap. Pick OffAlerts as the app and New Monitor Event as the event that sets everything else off.
- 02
Connect and test the trigger
Choose your OffAlerts connection and run the test. Zapier brings back the three most recent monitor events, so you map fields from a real one.
- 03
Add the log row
Pick your spreadsheet and its row action, then map the details the OffAlerts event carries into columns. Check the test result to see which ones arrive.
- 04
Add a follow-up card
If you like, create a card in your project board for each event so someone owns the follow-up. A second action makes the Zap multi-step, so it needs a paid plan.
- 05
Test, then publish
Run each step once and read what came back. When the row looks right, click Publish to switch the Zap on. Only events logged after that go through.
The OffAlerts trigger
1 event starts a Zap when something happens in OffAlerts. Zapier checks for them at the interval your plan allows.
New Monitor Event
Polling triggerIn Zapier“Triggers when a new monitor event triggers.”
Starts your Zap when one of your OffAlerts monitors logs a new event, for example when a site it watches goes offline. It is the only operation of the integration, so every OffAlerts Zap is built on it.
When the OffAlerts Zap breaks
Zapier links no help article to OffAlerts, and no rate limit is documented for it. What goes wrong is general Zapier behaviour applied to monitoring data.
Four general Zapier behaviours apply to a setup like this one. Read them before you publish, and open the Zapier troubleshooting guide when something still fails.
Past outages never come through
A Zap only reacts to events logged after it is switched on. Older monitor events stay in OffAlerts; copying them elsewhere is a separate, one-off job.A wave of events gets held back
When many monitors fire at once, during a wide outage for example, a sudden batch of events can be slowed by Zapier's flood protection.An event will not run twice
Zapier remembers what a polling trigger has already seen. An event that went through once will not start the Zap again on the next check.The second step needs a paid plan
On the free plan a Zap holds one trigger and one action. A filter, a second action or a search makes it multi-step, and the editor asks for a paid plan.
Need help automating OffAlerts with Zapier?
A person reads every message.
