Connect Adafruit IO to Dialmycalls

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

View example

Register a Contact for an IoT Alert

Add a person named in an Adafruit IO webhook payload to the Dialmycalls contact list for later alerting.

View example

Create a Group for a Device Cohort

Create a Dialmycalls contact group when an Adafruit IO webhook supplies a new cohort or device category.

View example

Register a Cohort Contact from Device Data

Add a contact from a webhook payload to a named Dialmycalls group when the payload supplies recipient and cohort details.

View example

Review Contacts for Device Operations

On a schedule, retrieve the Dialmycalls contact list for review alongside your Adafruit IO operations.

View example

Review Recipient Groups on a Schedule

Retrieve Dialmycalls groups on a recurring schedule to keep recipient organization visible for device operations.

View example

Review Do Not Contact Entries

Retrieve Dialmycalls do not contact entries on a schedule to review suppressed phone numbers or emails alongside device operations.

View example

Review Recent Device Related Calls

Retrieve Dialmycalls call records on a recurring schedule and summarize activity for operations review.

View example

Review Text Broadcast History

Retrieve Dialmycalls text broadcast records on a schedule for an operations history review.

View example

Check Dialmycalls Account Readiness

Retrieve main account details on a schedule to review account status and remaining credits for device operations.

Supported Triggers and Actions

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

Adafruit IO triggers

Dialmycalls actions

Recurring trigger

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

TriggerScheduled

Add Access Account

Add a sub-account with delegated dialing access.

ActionInstant

Webhook trigger

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

TriggerInstant

Add Contact

Add a contact to your contact list.

ActionInstant

Add Group

Create a group for organizing contacts.

ActionInstant

Delete Access Account

Delete a sub-account.

ActionInstant

Delete Caller ID

Permanently delete an existing caller ID.

ActionInstant

Delete Contact

Permanently delete a contact from your list.

ActionInstant

Delete Group

Delete an existing contact group.

ActionInstant

Delete Recording

Permanently delete a custom recording.

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.