Connect Adafruit IO to Dpd2

When something happens in Adafruit IO, Notis takes the next step in Dpd2. 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 Dpd2

View example

Add purchase context to device alerts

When an Adafruit IO alert arrives, check recent DPD purchases and summarize relevant customer or order context for follow-up.

View example

Review customers linked to sensor activity

On a schedule, review DPD customers matching identifiers supplied in your Adafruit IO operations data and summarize useful follow-up context.

View example

Check subscriber status during device escalations

When an Adafruit IO escalation arrives, verify a supplied DPD subscriber email or ID and include the result in the run report.

View example

Create a customer sales pulse for IoT operations

Run a recurring DPD customer listing and summarize patterns against the Adafruit IO operations context you provide.

View example

Verify DPD notifications before acting on device context

When a webhook carries an original DPD notification and signature, verify its authenticity and report the result with supplied Adafruit IO context.

Supported Triggers and Actions

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

Adafruit IO triggers

Dpd2 actions

Recurring trigger

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

TriggerScheduled

Get Storefront

Retrieve details about a storefront.

ActionInstant

Webhook trigger

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

TriggerInstant

List DPD Customers (Filtered)

Lists DPD customers with optional filters.

ActionInstant

List DPD Purchases

List purchases made through your account.

ActionInstant

List Storefronts

List all storefronts in your account.

ActionInstant

List Subscribers

List subscribers for a storefront.

ActionInstant

DPD: Ping API

Check the API status and connectivity.

ActionInstant

Verify DPD IPN Notification

Verifies whether an IPN notification came from DPD.

ActionInstant

Verify Subscriber

Checks a subscriber’s status using their email username or subscriber ID.

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.