Addigy Zapier integrationAutomate Addigy with Zapier.
The Addigy Zapier integration gives you 1 trigger, 2 actions and 2 searches. All five operations read data from your Apple device management account and none of them ever writes to it. The app works on the free Zapier plan.
Verified Trustpilot reviews · AI, automation & growth agency
What the Addigy Zapier integration actually does
The Addigy Zapier integration connects your Addigy account to the thousands of apps Zapier talks to. Zapier is a no-code automation tool: you describe once what should happen when something shows up in one app, and it runs on its own afterwards. On the Addigy side, everything visible in the editor is about reading data, not changing it.
A watch on system events. Get System Events checks your account for events that match a rule you set (a field, an operator, a value). An IT lead who wants a line in a shared log for every new match starts there, then sends the result to the app the team already reads.
A maintenance list on demand. Query Maintenance returns one page of maintenance items, sorted on the field you pick. Chained after the trigger, it lets a technician at a managed service provider attach the current maintenance list to each event the Zap catches.
A health snapshot. Query Monitoring, placed as a search step, fetches monitoring items so a later step can use them. Paired with a filter, it keeps the Zap quiet unless something you care about comes back.
What Zapier does not do here. None of the five operations creates, edits or deletes anything in Addigy: no new policy, no new user, no script assignment. If your plan is to push changes into your fleet, this connector will not do it. For a broader look at the tool itself, the Zapier review covers its strengths and limits, and n8n vs Zapier compares it with a self-hostable option.
Zapier vocabulary in one minute
Eight words come back on every Zapier page. Here is what each one means in plain English.
- Zap
- The automation you build: one trigger, then one or more actions that run each time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for it.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something for you.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan counts these.
- Polling vs instant
- A polling trigger is checked on a timer. An instant trigger is reported by the app the moment the event happens.
- Filter
- A step that lets the Zap carry on only when the incoming data meets your condition, and stops it otherwise.
- Search step
- A step that looks up something already stored in an app, so the steps after it can use what it found.
- Connection
- Your Addigy account linked to Zapier one time, then reused by every step that touches Addigy.
What an Addigy Zap really costs
Addigy is not a premium app, so it runs on the free plan. The bill depends on tasks, not on how often Zapier checks.
- Premium appNo, free plan accepted
- Free plan100 tasks a month, two-step Zaps only
- Trigger costNone
The trigger never costs a task, and checking for new data is free however often it happens. Each action that succeeds counts once, so a Zap with three actions uses three times more than a Zap with one. A failed action is not counted. The free plan gives 100 tasks a month and unlimited Zaps, but only two steps: one trigger and one action. Add a filter or a search and the Zap becomes multi-step, which needs a paid plan.
Connect your Addigy account in three steps
- 01
Open the connections page
In your Zapier account, go to Apps and click + Add connection. You need an existing Addigy account, plus access to whatever you do not own yourself but want the Zap to read.
- 02
Pick Addigy
Type Addigy in the search box of the dialog, select it in the results, then click Add connection. A new browser tab opens on the Addigy side, ready for the sign-in.
- 03
Sign in and grant access
Log in to Addigy in that tab and allow Zapier to reach the account. The connection then appears in your list and every Addigy step of every Zap can reuse it.
Your first Addigy Zap
GoalCatch matching system events, keep only the ones worth acting on, then fetch the list of installed MDM certificates.
- 01
Create the Zap
Start a new Zap and choose Addigy as the app that starts it, with Get System Events as the event. Select the Addigy connection made earlier.
- 02
Set the trigger rule
Fill Field, Operator and Value, then Page, Per Page and Sort Direction. For a date field, the value must use the
2006-01-02format. - 03
Test the trigger
Run the test. Zapier brings back the three most recent matching items from your account, so you map the next steps on real data instead of guesses.
- 04
Add the filter and the action
Add a filter from the plus icon, then Query Installed MDM Certificates with its page settings. The filter makes this a multi-step Zap, so it needs a paid plan.
- 05
Test, then publish
Test each step once and read what came back. When the output looks right, click Publish to switch the Zap on and let it run.
The Addigy trigger
1 event starts a Zap when something happens in Addigy. Zapier checks for them at the interval your plan allows.
Get System Events
Polling triggerIn Zapier“Allow to query for a set of system events.”
This trigger asks Addigy for system events that fit a condition you write yourself: a field, a comparison and a value. Every new event that matches starts the Zap, and Zapier keeps track of what it has already seen so the same event never runs twice.
2006-01-02 pattern or the rule never matches.Addigy actions
Addigy gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Query Installed MDM Certificates
ActionIn Zapier“Paginated request that returns list of installed certificates by mdm devices.”
Returns one page of certificates installed on devices managed through MDM, so a later step can store or forward the list.
Query Maintenance
ActionIn Zapier“Request for maintenance search”
Pulls maintenance items from Addigy, sorted on the field you choose, ready for the next step of the Zap.
Addigy searches
2 search steps look for data that already exists in Addigy, so a later step can use it.
A search step looks up data that already exists in Addigy and hands it to the following steps. In the editor, searches sit at the bottom of the Action event list, under the SEARCH heading. Each one comes with settings for the case where the lookup does not go as planned.
Query Custom Facts
SearchIn Zapier“Use a custom query to find specific facts”
Looks up custom facts in your Addigy account and passes them to the steps after it, sorted on the field you set.
Query Monitoring
SearchIn Zapier“Queries monitoring items”
Fetches monitoring items from Addigy so a filter or an action further down can act on them.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap there and skips the steps that depended on it. Switched on, the Zap goes on with nothing in hand.
- Create X if it doesn't exist yet?This box turns a search into a find-or-create on apps that support it. Addigy exposes no such variant, so neither search can create a missing item.
- If multiple search results are found?Three choices when several items match: keep the first one (the default), stop the Zap, or pass all of them on at once.
When an Addigy Zap breaks
Zapier links no help article to Addigy, so the known failure points are the general ones.
These four cases cover most surprises on a polling app like this one. Each comes from Zapier's own rules, not from guesswork. For a hands-on fix, the Zapier troubleshooting page walks through stuck Zaps.
No history is picked up
A Zap only reacts to what happens after you switch it on. Events already in Addigy before that moment stay where they are, and moving the backlog is a separate job.The Zap feeds itself
A Zap that writes into the place its own trigger watches sets itself off again and again, and burns through your task count fast.A sudden flood is held back
When a trigger returns a huge batch at once, after a bulk import or a migration, Zapier's flood protection can hold it back.Duplicates are not a bug
Zapier remembers what it has already seen on a polling trigger, so the same event does not start the Zap twice, even if it still matches your rule.
Need help automating Addigy with Zapier?
A person reads every message.
