Connect Adafruit IO to Cody

When something happens in Adafruit IO, Notis takes the next step in Cody. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Adafruit IO to Cody

View example

Turn an Adafruit IO Reading into a Cody Knowledge Note

Send a device reading to Notis and save a concise, timestamped note in Cody for later reference.

View example

Explain an Adafruit IO Alert with Cody

Send an alert and its context to Notis, then have Cody explain relevant company knowledge in a conversation.

View example

Open a Cody Review for a Device Incident

Start a Cody conversation when an incident payload arrives, so a team can review the device details in one thread.

View example

Save Device Maintenance Context in Cody

Convert a maintenance update sent to a Notis webhook into a structured Cody document for team reference.

View example

Create a Scheduled Cody Telemetry Summary

On a schedule, turn telemetry provided to Notis into a Cody document that calls out trends and missing context.

View example

Prepare a Recurring Cody Device Operations Review

Create a Cody conversation on a schedule to review available device data and organize the team's next questions.

Supported Triggers and Actions

Notis builds workflows that link Adafruit IO to Cody. A trigger fires from one place; an action lands in another.

Adafruit IO triggers

Cody actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Create Conversation

Starts a new conversation with a bot.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Create Document

Creates a text-based document in the knowledge base.

ActionInstant

Create Document From File

Creates a knowledge base document from an uploaded file.

ActionInstant

Create Document from Webpage

Creates a knowledge base document from a public webpage.

ActionInstant

Create Folder

Creates a folder to organize documents or conversations.

ActionInstant

Delete Conversation

Permanently deletes a conversation.

ActionInstant

Delete Document

Deletes a document.

ActionInstant

Get Conversation

Retrieves a conversation and its details.

ActionInstant

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.