ilert Zapier integrationAutomate ilert with Zapier.
The ilert Zapier integration gives you 1 trigger, 3 actions and 1 search, all built around incidents and on-call duty. Here is what each one does, what it costs in tasks, and the traps worth knowing before you publish a first automation.
Verified Trustpilot reviews · AI, automation & growth agency
What ilert and Zapier do together
Connecting ilert to Zapier means incidents stop living only inside your alerting tool. ilert handles alerting, on-call rotas and status pages; Zapier carries an incident to the other apps your team uses, or opens, accepts and closes incidents from those apps.
Three outcomes cover most setups. An incident feed somewhere people actually look: New or Updated Incident fires when an incident is created or changes state, and a following step posts it to chat or logs it in a sheet. Incidents opened from outside ilert: Create Incident lets a form, a ticket or a monitoring tool without a native ilert link raise an incident, as long as it can hand over a summary. The right person named in the message: Find User on Call looks up who holds a given on-call schedule, so a notification can address that person instead of a whole channel.
The two remaining actions close the loop. Accept Incident and Resolve Incident move an open incident forward from another app, which suits a team that acknowledges work in a ticketing tool and wants ilert to follow.
Now the limits. Zapier offers no way here to read alert sources, schedules or users as events: the only trigger is about incidents. There is no step to edit an incident's summary after the fact, and nothing to manage status pages, even though ilert itself does that. If your project hinges on one of those, Zapier will not get you there with this app.
Comparing tools? The ilert Make integration page covers the same app on Make, and the Make vs Zapier comparison lays out how the two platforms differ.
Zapier vocabulary in one minute
Eight words come back on every line of this page. Here they are in plain English.
- Zap
- A rule you set once on Zapier: when this happens in ilert or elsewhere, do that, then that. It runs on its own every time.
- Trigger
- The starting signal. For ilert on Zapier there is exactly one: an incident that opens or changes state.
- Action
- Each step that follows the signal and does real work: posting the alert, opening a ticket, closing an incident.
- Task
- The unit Zapier bills. One task equals one action completed successfully, and your plan allows a set number of them.
- Polling vs instant trigger
- Polling: Zapier knocks on the app's door at set intervals. Instant: the app rings Zapier itself. ilert's incident trigger rings.
- Filter
- A checkpoint between steps. Only incidents matching your rule, say a given priority, go further; the others end the run there.
- Search step
- A step that looks up something already stored in an app, so the steps after it can reuse what it found.
- Connection
- The saved sign-in that lets Zapier act on your ilert account. Made once, then picked from a menu in each ilert step.
What an ilert Zap really costs
Zapier bills by tasks, not by Zaps or incidents. ilert sits outside the premium list, so a free account can already use it.
- TriggerFree, never counted
- Each successful action1 task
- Free plan100 tasks a month, 2-step Zaps only
- Premium appNo
The incident trigger costs nothing, however many incidents come through. Each action that succeeds counts as one task; one that fails is not billed. A Zap that posts to chat and then logs to a sheet uses two tasks per incident. The free plan gives 100 tasks a month and unlimited Zaps, but only two steps: one trigger, one action. Paging the person on call needs the search on top of the message, and that third step alone moves you to a paid plan, as a filter would. The polling grid (15 minutes on Free, 2 on Professional, 1 on Team and Enterprise) does not apply here, since the only ilert trigger is instant.
Connect your ilert account to Zapier
- 01
Open the Apps page
Head to the Apps page of Zapier and press + Add connection. In the dialog that pops up, type ilert and choose it among the results; the connection itself is made in the next two moves.
- 02
Sign in to ilert
Click Add connection. ilert opens in a new tab and asks you to sign in. Use an account that can reach the alert sources and on-call schedules your Zaps will rely on.
- 03
Grant access
Confirm that Zapier may access the account. Back on the Apps page, ilert now shows up in your list, ready to be selected when you build the first Zap.
Your first ilert Zap: page the person on call in Slack
GoalWhen a high-priority incident opens, look up who is on call and send that person a direct message in Slack.
- 01
Create the Zap and set the trigger
Start a new Zap, pick ilert as the app and
New or Updated Incidentas the event. Choose the alert source to watch and the event types you want. - 02
Test the trigger
Run the test. Zapier brings back the three most recent items from the connected account, so you map fields on a real incident rather than a guess.
- 03
Add a filter
From the plus icon, add Filter. Pick a value you saw in the test, the rule, and what it must equal. Text rules only work on text, so match the type.
- 04
Find who is on call
Add the
Find User on Callsearch and pick the on-call schedule of the team that owns the service. Test it to check that a real person comes back. - 05
Message that person
Add Slack with Send Direct Message, map the person found and the incident summary, test once, then click Publish. This Zap has four steps, so it needs a paid plan.
The ilert trigger
1 event starts a Zap when something happens in ilert, and one of them is instant: the app calls Zapier straight away, whatever your plan.
New or Updated Incident
Instant triggerIn Zapier“Triggers when new incidents are created, or when existing incidents change state.”
This trigger starts your Zap whenever ilert opens a new incident, and again whenever an existing one moves to another state. You choose which alert source to watch and which kinds of events count, so a quiet source never wakes the Zap.
The ilert actions
ilert gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Accept Incident
ActionIn Zapier“Accepts an incident in iLert”
Marks an open incident as accepted, so ilert shows that someone has taken it.
Create Incident
ActionIn Zapier“Creates an incident in iLert.”
Opens a fresh incident in ilert from anything another app sends, and the summary you map becomes the incident summary.
Resolve Incident
ActionIn Zapier“Resolves an incident in iLert”
Closes an open incident in ilert once the problem has been fixed somewhere else.
The ilert search
1 search step looks for data that already exists in ilert, so a later step can use it.
A search step finds something that already exists and hands it to later steps. In the editor, searches sit at the bottom of the Action event list, under SEARCH. Three settings decide what happens when the result is not a clean single match.
Find User on Call
SearchIn Zapier“Find the user on call for a specific schedule.”
Looks up whoever is currently on duty for the on-call schedule you pick, and passes that person to the next steps.
The three settings every search exposes
- Successful if no search results are found?Left on its default, an empty result stops the Zap at the search and skips the steps that depend on it. Switched on, the Zap carries on without a result.
- Create X if it doesn't exist yet?This box turns a search into a find-or-create. ilert offers no such variant on Find User on Call, so you will not see it here.
- If multiple search results are found?Keep the first match (the default), stop the Zap, or pass every match on to the next steps at once.
When an ilert Zap breaks
Zapier links no help article to ilert and documents no app-specific limit, so the failures to expect are the general ones.
Four cases account for most surprises. If something looks off, the Zapier troubleshooting guide walks through the fixes.
Old incidents are never picked up
Incidents opened before the Zap went live never reach it. Last month's outages stay in ilert; copying that history elsewhere is its own project.The Zap feeds itself
Put Accept or Resolve after the incident trigger and each state change sets the Zap off again. Keep ilert actions out of Zaps that watch ilert incidents.A burst gets held back
When a trigger suddenly sends a huge batch, after a bulk import or a migration, Zapier's flood protection can hold the runs back.The filter never passes
Filter rules are typed. A number rule on a text value, or the reverse, blocks every run, and the Zap looks dead while incidents keep coming.
Need help automating ilert with Zapier?
A person reads every message.
