Connect Adafruit IO to Desktime

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

View example

Start a DeskTime task from an Adafruit IO work signal

Use an Adafruit IO webhook to start tracking a known DeskTime project when a device sends a work-start signal.

View example

Stop DeskTime tracking from an Adafruit IO signal

Stop a specified DeskTime project task when an Adafruit IO webhook reports that your work session has ended.

View example

Create a DeskTime project from an Adafruit IO request

Turn a project setup request received through an Adafruit IO webhook into a DeskTime project with an optional initial task.

View example

Review active DeskTime projects on a schedule

Have Notis retrieve the active DeskTime projects and related tasks on a recurring schedule for a concise review.

View example

Check DeskTime account settings on a schedule

Retrieve DeskTime company details, work settings, timezone, and timestamp on a recurring schedule for an account check.

View example

Review the DeskTime team roster on a schedule

Retrieve employee names, roles, and statuses from DeskTime on a recurring schedule for a lightweight roster review.

View example

Check DeskTime API availability on a schedule

Ping the DeskTime API on a recurring schedule and receive a report confirming whether it is reachable and responsive.

Supported Triggers and Actions

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

Adafruit IO triggers

Desktime actions

Recurring trigger

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

TriggerScheduled

Create Project with Optional Task

Create a project, optionally with an initial task.

ActionInstant

Webhook trigger

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

TriggerInstant

Get Account Details

View the company's account settings, work schedule, and timezone.

ActionInstant

Get All Company Employees

View the company's employee roster, roles, and statuses.

ActionInstant

Get Employee

Retrieves one employee’s information and tracking data for a date, or the current user’s data.

ActionInstant

Get Employee Projects

View an employee's project assignments and time tracking for a date.

ActionInstant

Get Employee Apps

Retrieves an employee’s tracked app usage for a date, or the current user’s data.

ActionInstant

Get Employee Projects and Apps

View an employee's daily work, attendance, and productivity summary.

ActionInstant

Get Projects List

View all active company projects and their tasks.

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.