Adafruit IO, worked by an AI employee
Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Adafruit IO account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.
- Internet Of Things
- Connects with a key
- 21 ready-made tools
- Asked in Slack or Teams
An illustration of how the conversation reads, not a transcript from a client account.
What Adafruit IO is
Adafruit IO is a cloud platform for storing, visualizing, and acting on data from connected devices and Internet of Things projects.
You paste in a key from your own Adafruit IO account. It is kept encrypted, and you can withdraw it from inside Adafruit IO whenever you like.
One message in, the work done in Adafruit IO.
- 01
You ask
You message your AI employee in the chat your team already has open, in one sentence, in your own words.
- 02
It works out the step
It decides what the job needs in Adafruit IO. You do not pick anything from a menu or wire anything together.
- 03
It does the work
Signed in to your own Adafruit IO account, inside the access you granted it, doing the thing you asked for.
- 04
It reports back
It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.
What it can do in Adafruit IO
These are the ready-made tools your AI employee already has in Adafruit IO. It is not limited to them, but it never has to be taught these.
- Add Feeds to GroupSequentially add 1-10 existing feeds to one group using one documented provider request per feed. This is non-atomic: processing stops after the first failed or ambiguous attempt,
- Create DashboardCreate a dashboard for visualizing and controlling feed data.
- Create FeedCreate a feed, optionally within an existing group.
- Create GroupCreate a group for organizing feeds.
- Delete DashboardPermanently delete one dashboard by exact key.
- Delete Data PointPermanently delete one feed data point by ID.
- Delete Data PointsPermanently delete 1-30 feed data points sequentially through Adafruit IO's single-data-point DELETE endpoint, bounded by the Free-plan limit of 30 data mutations per minute. This
- Delete FeedPermanently delete one feed and its retained data by exact feed key.
- Delete GroupPermanently delete one group by exact key.
- Get Account StatusReturn compact identity, plan limits, and current data-write throttle usage for the connected Adafruit IO account.
- Get DashboardsList dashboards, or retrieve one dashboard and its blocks by key.
- Get Data PointRetrieve one feed data point by its exact ID.
- Get FeedsList feeds, or retrieve one feed by key with optional data summary details.
- Get GroupsList groups with feed summaries, or retrieve one group by key.
- List Feed DataReturn one newest-first page of feed data with an opaque cursor for the next older page.
- Publish Feed DataPublish one or multiple timestamped values to a feed, using the batch endpoint only when multiple points are supplied.
- Remove Feeds from GroupSequentially remove 1-10 feeds from one group using one documented provider request per feed. This is non-atomic: processing stops after the first failed or ambiguous attempt, whil
- Update DashboardUpdate an existing dashboard by exact dashboard key.
- Update Data PointReplace the value and optional metadata of one existing feed data point.
- Update FeedUpdate an existing feed by exact feed key.
- Update GroupUpdate an existing group by exact group key.
You stay the boss of your Adafruit IO account.
Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.
How we handle your data- It signs in to your own Adafruit IO account. You are not moving anything into ours.
- You grant access one app at a time, and you can take it back the same way.
- Everything it does in Adafruit IO is written down, with what it did and when.
- Anything you tell it to check with you first, it checks with you first.
It works in Adafruit IO and the rest of your software in the same job
A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.
Questions people ask about Adafruit IO
- Can an AI employee really work inside Adafruit IO?
- Yes. It signs in to your own Adafruit IO account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
- Do I have to move anything out of Adafruit IO?
- No. Nothing moves and nothing is replaced. Your records stay in Adafruit IO, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
- How does it get into my Adafruit IO account?
- You paste in a key from your own Adafruit IO account. It is kept encrypted, and you can withdraw it from inside Adafruit IO whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
- What can it actually do in Adafruit IO?
- It has 21 ready-made tools in Adafruit IO today, among them Add Feeds to Group, Create Dashboard and Create Feed. The full list is on this page. It is not limited to those, but it never has to be taught them.
- Can it use Adafruit IO and the rest of my software in the same job?
- Yes, and that is usually the point. Reading a message in one app, checking a record in Adafruit IO and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
- Who decides what it is allowed to do in Adafruit IO?
- You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Adafruit IO is written down with what it did and when.