Connect Adrapid to Bolt iot

When something happens in Adrapid, Notis takes the next step in Bolt iot. 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 Adrapid to Bolt iot

View example

Check Bolt connectivity before an Adrapid render alert

When an Adrapid webhook reports a completed or failed asset render, verify the named Bolt device is online before any follow-up automation.

View example

Read a sensor after an Adrapid campaign export

When Adrapid sends a webhook with a finalized campaign asset and a sensor check request, read the specified analog pin on the named Bolt device.

View example

Toggle a Bolt indicator when an Adrapid video is ready

When Adrapid posts a video-ready webhook, set a specified Bolt digital pin high or low to signal the production state.

View example

Read Bolt serial data after an Adrapid failure

When an Adrapid webhook reports a failed generation or API request, read incoming serial data from the specified Bolt device that has already been initialized for UART.

View example

Send an Adrapid job id to Bolt UART

When Adrapid sends a webhook for a selected asset job, transmit its supplied job id or control text over UART to the specified Bolt device.

View example

Run a Bolt serial round trip for an Adrapid command

When Adrapid supplies a device command in a webhook, send it over Bolt UART and capture the immediate response.

View example

Review Bolt readiness from a scheduled Adrapid export

On a schedule, inspect a supplied Adrapid export containing recent asset jobs and target Bolt device ids, then check each specified device online status.

View example

Take a scheduled sensor snapshot for Adrapid assets

On a schedule, read specified analog pins on Bolt devices listed in a supplied Adrapid asset export and report the readings beside each asset.

View example

Reset a Bolt indicator from Adrapid status data

On a schedule, read a supplied Adrapid status export and set the specified Bolt digital pin HIGH or LOW exactly as instructed.

Supported Triggers and Actions

Notis builds workflows that link Adrapid to Bolt iot. A trigger fires from one place; an action lands in another.

Adrapid triggers

Bolt iot actions

Recurring trigger

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

TriggerScheduled

Analog Read

Reads the analog value from a device pin.

ActionInstant

Webhook trigger

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

TriggerInstant

Check Bolt device online status

Checks whether a device is online.

ActionInstant

Bolt IoT Digital Write

Sets a device’s digital pin to HIGH or LOW.

ActionInstant

Bolt IoT Serial Read

Reads incoming serial data from a device.

ActionInstant

Bolt IoT Serial Write

Sends serial data to a device.

ActionInstant

Bolt IoT Serial Write & Read

Sends serial data to a device and reads its reply.

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.