Automate Adafruit IO
HumDay reads Adafruit IO’s own published API description and derives 71 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What Adafruit IO is
### The Internet of Things for Everyone The Adafruit IO HTTP API provides access to your Adafruit IO data from any programming language or hardware environment that can speak HTTP. The easiest way to get started is with [an Adafruit IO learn guide](https://learn.adafruit.com/series/adafruit-io-basics) and [a simple Internet of Things capable device like the Feather Huzzah](https://www.adafruit.com
API host: io.adafruit.com
What HumDay can do in Adafruit IO
42 documented operations change something in Adafruit IO.
- POSTCreate a new Feed
/{username}/feeds - POSTCreate a new Group
/{username}/groups - POSTCreate a new Token
/{username}/tokens - POSTCreate a new Trigger
/{username}/triggers - POSTCreate a new Dashboard
/{username}/dashboards - POSTSend data to a feed via webhook URL.
/webhooks/feed/:token - POSTSend arbitrary data to a feed via webhook URL.
/webhooks/feed/:token/raw - POSTCreate multiple new Data records
/{username}/feeds/{feed_key}/data/batch - DELETEAll activities for current user
/{username}/activities - POSTCreate new Data
/{username}/feeds/{feed_key}/data - POSTCreate new data for multiple feeds in a group
/{username}/groups/{group_key}/data - POSTCreate a new Feed in a Group
/{username}/groups/{group_key}/feeds - POSTCreate a new Block
/{username}/dashboards/{dashboard_id}/blocks - POSTCreate multiple new Data records in a feed belonging to a particular group
/{username}/groups/{group_key}/feeds/{feed_key}/data/batch - POSTAdd an existing Feed to a Group
/{username}/groups/{group_key}/add - POSTCreate new Data in a feed belonging to a particular group
/{username}/groups/{group_key}/feeds/{feed_key}/data - DELETEDelete an existing Token
/{username}/tokens/{id} - PATCHUpdate properties of an existing Token
/{username}/tokens/{id} - PUTReplace an existing Token
/{username}/tokens/{id} - DELETEDelete an existing Trigger
/{username}/triggers/{id} - PATCHUpdate properties of an existing Trigger
/{username}/triggers/{id} - PUTReplace an existing Trigger
/{username}/triggers/{id} - DELETEDelete an existing Dashboard
/{username}/dashboards/{id} - PATCHUpdate properties of an existing Dashboard
/{username}/dashboards/{id} - PUTReplace an existing Dashboard
/{username}/dashboards/{id} - DELETEDelete an existing Feed
/{username}/feeds/{feed_key} - PATCHUpdate properties of an existing Feed
/{username}/feeds/{feed_key} - PUTReplace an existing Feed
/{username}/feeds/{feed_key} - DELETEDelete an existing Group
/{username}/groups/{group_key} - PATCHUpdate properties of an existing Group
/{username}/groups/{group_key} - PUTReplace an existing Group
/{username}/groups/{group_key} - POSTRemove a Feed from a Group
/{username}/groups/{group_key}/remove - DELETEDelete existing Data
/{username}/feeds/{feed_key}/data/{id} - PATCHUpdate properties of existing Data
/{username}/feeds/{feed_key}/data/{id} - PUTReplace existing Data
/{username}/feeds/{feed_key}/data/{id} - DELETEDelete an existing Block
/{username}/dashboards/{dashboard_id}/blocks/{id} - PATCHUpdate properties of an existing Block
/{username}/dashboards/{dashboard_id}/blocks/{id} - PUTReplace an existing Block
/{username}/dashboards/{dashboard_id}/blocks/{id} - POSTCreate a new Permission
/{username}/{type}/{type_id}/acl - DELETEDelete an existing Permission
/{username}/{type}/{type_id}/acl/{id} - PATCHUpdate properties of an existing Permission
/{username}/{type}/{type_id}/acl/{id} - PUTReplace an existing Permission
/{username}/{type}/{type_id}/acl/{id}
What HumDay can read from Adafruit IO
These are the operations a schedule or a trigger can watch.
- GETGet information about the current user
/user - GETGet the user's data rate limit and current activity level.
/{username}/throttle - GETAll feeds for current user
/{username}/feeds - GETAll groups for current user
/{username}/groups - GETAll tokens for current user
/{username}/tokens - GETAll triggers for current user
/{username}/triggers - GETAll activities for current user
/{username}/activities - GETAll dashboards for current user
/{username}/dashboards - GETGet activities by type for current user
/{username}/activities/{type} - GETAll feeds for current user in a given group
/{username}/groups/{group_key}/feeds - GETAll blocks for current user
/{username}/dashboards/{dashboard_id}/blocks - GETReturns Token based on ID
/{username}/tokens/{id} - GETReturns Trigger based on ID
/{username}/triggers/{id} - GETReturns Dashboard based on ID
/{username}/dashboards/{id} - GETGet feed by feed key
/{username}/feeds/{feed_key} - GETReturns Group based on ID
/{username}/groups/{group_key} - GETGet all data for the given feed
/{username}/feeds/{feed_key}/data - GETGet detailed feed by feed key
/{username}/feeds/{feed_key}/details - GETLast Data in Queue
/{username}/feeds/{feed_key}/data/last - GETNext Data in Queue
/{username}/feeds/{feed_key}/data/next - GETChart data for current feed
/{username}/feeds/{feed_key}/data/chart - GETFirst Data in Queue
/{username}/feeds/{feed_key}/data/first - GETLast Data in MQTT CSV format
/{username}/feeds/{feed_key}/data/retain - GETPrevious Data in Queue
/{username}/feeds/{feed_key}/data/previous - GETReturns data based on feed key
/{username}/feeds/{feed_key}/data/{id} - GETReturns Block based on ID
/{username}/dashboards/{dashboard_id}/blocks/{id} - GETAll data for current feed in a specific group
/{username}/groups/{group_key}/feeds/{feed_key}/data - GETAll permissions for current user and type
/{username}/{type}/{type_id}/acl - GETReturns Permission based on ID
/{username}/{type}/{type_id}/acl/{id}
How automating Adafruit IO works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live Adafruit IO account.
- Grant access, then go live. You approve the specific Adafruit IO operations it may use — and only those.
Popular Adafruit IO integrations
Connect Adafruit IO to the tools people pair it with most.
- Adafruit IO and OData for namespace microsoft.graphintegration
- Adafruit IO and Cloudflareintegration
- Adafruit IO and NetBoxintegration
- Adafruit IO and GitHubintegration
- Adafruit IO and Mistintegration
- Adafruit IO and Loket.nlintegration
- Adafruit IO and Atlassian The Jira Cloud platformintegration
- Adafruit IO and Magento B2Bintegration
- Adafruit IO and Stripeintegration
- Adafruit IO and Zuora Reference Billingintegration
- Adafruit IO and bunqintegration
- Adafruit IO and DocuSignintegration
Automate Adafruit IO with these
- Gambitcomm MIMIC356 operations
- Meraki Dashboard263 operations
- ClearBlade220 operations
- Influxdata Influx OSS197 operations
- Intellifi Brain77 operations
- Ijenko IoE² IoT to create end user applications67 operations
- smart me64 operations
- Opto22 PAC Control55 operations
- KeyServ24 operations
- Hardware Sentry TrueSight Presentation Server23 operations
- Netatmo19 operations
- dweet.io13 operations
Categories
Questions about Adafruit IO automation
- Can HumDay connect to Adafruit IO?
- Yes. HumDay reads Adafruit IO's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 71 operations are documented.
- Do I need to write code to automate Adafruit IO?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Adafruit IO account.
- What can HumDay do in Adafruit IO?
- 42 of the 71 documented operations change something in Adafruit IO, and 29 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Adafruit IO account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Adafruit IO is held behind that approval.
Where this came from
The operations above are read from a published API description for Adafruit IO at raw.githubusercontent.com/adafruit/io-api/gh-pages/v2.json. Descriptions are the provider’s own words, not ours. Last published 2021-06-21.