Who can connect Adafruit IO for the company?

A company connection is installed by an administrator.

Can I connect Adafruit IO just for myself?

Anyone can install a personal connection within the plan’s limit and use it in their own conversations.

Do I use my Adafruit IO account or a company account?

Yours: Adafruit IO requires an API key, and each person registers their own, generated in their account. The key is stored encrypted and nobody sees it, not even the administrator.

Does Skyller do everything on that action list?

The list is what the vendor offers. What the AI uses in your company is what the administrator turned on, for the groups they defined — Skyller never widens the connector's access.

Does an action in Adafruit IO happen without anyone approving it?

Reads happen within permission. Write actions have a risk level; sensitive ones show a confirmation card before running and are recorded. The company adjusts the classification when needed.

Adafruit IO does not show up in my company's catalog.

The administrator may have hidden the integration for your company, or the vendor may have discontinued it — in that case it leaves the catalog on the next synchronization, without deleting what was already connected. Talk to whoever administers Skyller in your company.

Integration · Other

Adafruit IO in Skyller.

Connect Adafruit IO to Skyller and the AI starts reading from and acting in it through the functions your company enables — with each person's own login, approval before sensitive actions and a record of every call. Below, the actions and events the vendor publishes, what it takes to start and where this fits into the work.

Talk to a specialist Try it free

Actions and events

Adafruit IO

Other

Adafruit IO is a cloud platform for storing, visualizing, and acting on data from connected devices and Internet of Things projects.

Actions: 21
Events: 0

Source: Composio catalog
Login: API key
Country: Global — no specific country
Actions list: re-read from the vendor every 24 hours
Official site: io.adafruit.com

Description and action names are the ones the vendor publishes, in English; action descriptions are shown summarized. Skyller does not alter that content.

21 ACTIONS

published by the vendor; the company enables only the necessary ones

0 EVENTS

triggers the system can send, when the vendor offers them

API KEY

each person signs in with their own credential, encrypted

APPROVAL BY RISK

sensitive actions show a card before running

Live proof

One request, one query in Adafruit IO and one approval.

The scene shows the path of a request; the exact actions depend on the functions your company enables in Adafruit IO.

Input
A team member asks, in the conversation, for something that today requires opening Adafruit IO — inside their area's space, with their login.
What Skyller does
1. 01Picks, among the enabled functions, a query action and looks the information up in Adafruit IO with the person's own credential.
2. 02If the request requires writing something in Adafruit IO, acts within permission; if the function is sensitive, it first shows the card and waits for Approve.
3. 03Returns the result in the conversation and records who asked, which action was used and when.
Result
Adafruit IO stops being an open tab and starts answering inside the conversation — through the functions your company enabled.

Good to know

The available actions are the ones the vendor publishes for Adafruit IO; in your company only the functions turned on by the administrator are available.
If a write action is not classified as sensitive, it may run without a card; the classification is adjustable by the company.
Being in this catalog does not mean being installed, with a valid login, working in your company.

Illustrative scene with fictitious data; no action is named because the choice depends on the functions your company enables.

Where this helps your work

Adafruit IO inside the conversation where the work happens.

Three common situations for people who use Adafruit IO every day. What Skyller does in each one depends on the functions your company turns on.

Needing the information now

“What is recorded in Adafruit IO about this?”

The person asks in the conversation and Skyller queries Adafruit IO with their login, through the enabled read functions, and answers with what it found.

System data in the answer

Recording the result

“Log this in Adafruit IO.”

Creating or changing a record is a write action; with the function set to ask for approval, Skyller shows the card with what it is about to do and waits for Approve before touching Adafruit IO.

Action with approval

Administering

“Enable only what this team needs.”

The administrator connects Adafruit IO once, turns on the necessary functions, restricts them to groups and follows the record of every call.

Function by function, with a record

Actions and events

What the vendor offers in Adafruit IO.

Names as the vendor publishes them, in English, with the description summarized to its first sentence. In your company, the administrator turns on only the necessary actions; none of them runs without permission, and sensitive ones go through approval.

Showing 12 of 21

Add Feeds to Group
ADAFRUIT_IO_ADD_FEEDS_TO_GROUP
Sequentially add 1-10 existing feeds to one group using one documented provider request per feed.
Create Dashboard
ADAFRUIT_IO_CREATE_DASHBOARD
Create a dashboard for visualizing and controlling feed data.
Create Feed
ADAFRUIT_IO_CREATE_FEED
Create a feed, optionally within an existing group.
Create Group
ADAFRUIT_IO_CREATE_GROUP
Create a group for organizing feeds.
Delete Dashboard
ADAFRUIT_IO_DELETE_DASHBOARD
Permanently delete one dashboard by exact key.
Delete Data Point
ADAFRUIT_IO_DELETE_DATA_POINT
Permanently delete one feed data point by ID.
Delete Data Points
ADAFRUIT_IO_DELETE_DATA_POINTS
Permanently 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.
Delete Feed
ADAFRUIT_IO_DELETE_FEED
Permanently delete one feed and its retained data by exact feed key.
Delete Group
ADAFRUIT_IO_DELETE_GROUP
Permanently delete one group by exact key.
Get Account Status
ADAFRUIT_IO_GET_ACCOUNT_STATUS
Return compact identity, plan limits, and current data-write throttle usage for the connected Adafruit IO account.
Get Dashboards
ADAFRUIT_IO_GET_DASHBOARDS
List dashboards, or retrieve one dashboard and its blocks by key.
Get Data Point
ADAFRUIT_IO_GET_DATA_POINT
Retrieve one feed data point by its exact ID.

Before you start

What your company needs to use Adafruit IO.

Login: Each person enters their own Adafruit IO API key, generated in their account. The key is stored encrypted and nobody sees it, not even the administrator.
Who installs: An administrator connects Adafruit IO for the company and shares it with people or groups. Anyone can connect just for themselves, within the plan's limit.
Functions: 21 published actions: the administrator turns on only the necessary ones. Sensitive ones ask for confirmation before running.
Plan: Counts as a company or personal connection within the plan's allowance; the larger plans have no cap. The connections-per-plan table is on the catalog page.

Questions from the people who decide

Common doubts before connecting Adafruit IO.

Related integrations

Other Other integrations.

See the full catalog

Next step

Connect Adafruit IO and try it with your team.

Try it free with your team or book a demo: together we pick the Adafruit IO functions to enable and show the first approved action, with fictitious data.