Connect Abstract to Desktime

When something happens in Abstract, 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 Abstract to Desktime

View example

Turn validated client requests into DeskTime projects

Check incoming client contact details with Abstract, then create a DeskTime project with an optional first task.

View example

Start DeskTime when a work request is ready

Check a supplied contact detail and use an incoming work request to start tracking a specified DeskTime project and optional task.

View example

Stop DeskTime when work is marked finished

Use a completion request to stop tracking a specified DeskTime project and optional task, with Abstract available to process supplied text.

View example

Check DeskTime account settings on a schedule

Periodically retrieve DeskTime account details, including company name, work settings, timezone, and timestamp.

View example

Review the DeskTime employee roster regularly

Retrieve the company employee roster, including roles and statuses, on a recurring schedule.

View example

Collect DeskTime employee data for review

Retrieve DeskTime data for all employees on a schedule and use Abstract to process returned text when useful.

View example

Review employee project time for a chosen date

Retrieve employee project assignments, durations, and statuses for a specific date on a recurring schedule.

View example

Review an employee's DeskTime projects and apps

Retrieve combined project and application usage data for a specified employee and date on a schedule.

View example

Keep a recurring overview of active DeskTime projects

Retrieve the company's active DeskTime projects and related tasks on a recurring schedule.

Supported Triggers and Actions

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

Abstract 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

ActionInstant

Get Employee Projects

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

ActionInstant

Get Employee Apps

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.