myDevices Zapier integrationAutomate myDevices with Zapier.
The myDevices Zapier integration offers 4 triggers, 0 actions and 0 searches. It reads from your IoT platform: telemetry from a device, new devices and new locations, and passes them on to other apps. Here is how each trigger behaves, what it costs and what it cannot do.
Verified Trustpilot reviews · AI, automation & growth agency
What the myDevices Zapier integration is good for
myDevices is a platform for plug-and-play connected devices. On Zapier it works in one direction only: something happens in your myDevices account, a reading comes in or a device is added, and a Zap carries that information into another app. Nothing travels back the other way.
Three outcomes cover what you can build. A running log of sensor readings. Device Telemetry Data - Polling picks up new data from a chosen device, and an action in a spreadsheet stores each reading as a row you can chart or share. An inventory that keeps itself current. Location Devices - Polling notices each new device at a company, so a list kept elsewhere grows without anyone retyping it. New sites announced to the team. Company Locations - Polling fires on each new location, which can post a note where your team reads.
Now what the app page does not spell out. myDevices has no action on Zapier: a Zap cannot create a device, change a setting or write anything into myDevices. There is no search either. And all four triggers are polling triggers, so nothing arrives instantly: on the free plan, Zapier checks every 15 minutes. If you need to react to a reading as it happens, that pace is the first thing to weigh.
If you are still weighing Zapier itself, see our Zapier review.
Zapier vocabulary in one minute
Seven words come back on this page. Here they are once, in plain English.
- Zap
- The automation you build on Zapier: 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, such as new telemetry from a myDevices sensor. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does once started: the step that writes, sends or moves something for you, here always in another app.
- Task
- The unit Zapier bills. Each action that completes successfully counts as one task against your plan.
- Polling trigger
- A trigger Zapier checks on a timer, keeping only what it has not seen yet. An instant trigger is reported by the app itself instead.
- Filter
- A step that lets the Zap continue only when what arrived meets the condition you set, and stops it otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action or a filter makes one, and it then needs a paid plan.
What a myDevices Zap really costs
myDevices is not a premium app, so it runs on the free plan. Zapier bills in tasks, and myDevices itself never spends one.
- myDevices trigger0 tasks
- Each successful action1 task
- Free plan100 tasks a month, two-step Zaps
- Premium appNo
A myDevices trigger costs nothing, however often Zapier checks for new data. Only the action that follows, in another app, counts: one task each time it succeeds, none when it fails. The free plan gives 100 tasks a month and unlimited Zaps of two steps each. Add a filter or a second action and the Zap turns multi-step, which needs a paid plan. All four myDevices triggers are polling triggers, so the interval grid below applies to every one of them.
Connect myDevices to Zapier in three steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. You need a myDevices account, plus read or write access on anything you do not own yourself and want the Zap to touch.
- 02
Pick myDevices
Search for myDevices in the dialog, select it, then click Add connection. A new tab opens on the myDevices side, which is where you actually sign in.
- 03
Sign in and grant access
Log in to myDevices in that tab and grant Zapier access to the account. Every myDevices trigger in every Zap then reuses this connection, so you only do it once.
Your first Zap: a sensor log in a spreadsheet
GoalEach new reading from one myDevices sensor that passes your filter becomes a row in a spreadsheet you can sort, chart or share.
- 01
Set the trigger
Create a Zap, choose myDevices and Device Telemetry Data - Polling, then your connection. Pick the Company, Company Location, Device and History Range, all four required.
- 02
Test it on real data
Run the trigger test. Zapier brings back the three most recent items of the connected account, so you map fields on real readings rather than a guess.
- 03
Add the filter
Add a Filter step from the plus icon and set the field, the rule and the value. A filter makes the Zap multi-step, so this step needs a paid plan.
- 04
Add the spreadsheet action
Pick your spreadsheet app and its action to add a row, then place the values of the reading that came back from the test into the right columns.
- 05
Test, then publish
Test the action once and read what came back before going further. Then publish the Zap to switch it on; only readings that arrive afterwards are logged.
myDevices triggers on Zapier
4 events start a Zap when something happens in myDevices. Zapier checks for them at the interval your plan allows.
Company Locations - Polling
Polling triggerIn Zapier“Triggers when a new location is added.”
Starts the Zap each time a new location is added under a company in myDevices, so the new site can be recorded or announced elsewhere.
Device Telemetry Data - Polling
Polling triggerIn Zapier“Triggers when new device telemetry data is available.”
Picks up new telemetry data from a device in your myDevices account and hands each new item to the next steps of the Zap.
Location Devices - Polling
Polling triggerIn Zapier“Triggers when a new device is created.”
Fires when a new device is created in myDevices for the company you select, which makes it the natural start for an equipment list.
User Companies - Polling
Polling triggerIn Zapier“Triggers when a dropdown company is selected.”
Zapier describes this one as firing when a company is selected from a dropdown. That single line is all the documentation says about it.
When a myDevices Zap breaks
Zapier attaches no help article to myDevices and documents no limit specific to the app. The cases below come from the general rules every Zap follows.
Four of them matter for a Zap that reads from connected devices. If one shows up, our Zapier troubleshooting guide is the next stop.
Past readings are not picked up
A Zap only reacts to what happens after you switch it on. Readings, devices or locations that already existed are not sent; moving that backlog is a separate job.A Zap that sets itself off
As a general precaution: a Zap that writes into the very place its own trigger watches can start itself again and again, and burns through tasks fast.A big batch gets held back
If a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold those items back.Same item, one run
On a polling trigger, Zapier keeps track of what it has already seen, so the same item does not start the Zap twice.
Need help automating myDevices with Zapier?
A person reads every message.
