Connect Airtop to Cal

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

View example

Check Calendar Before Accepting an Inquiry

Read a meeting inquiry from a website, then check calendar availability before you reply.

View example

Review Pending Meeting Requests

On a schedule, use Airtop to find pending meeting requests and check their proposed times against Cal availability.

View example

Add a Requested Booking Participant

Review a booking page for an explicitly requested additional participant, then add them to the existing Cal booking.

View example

Confirm a Reviewed Pending Booking

Review booking details in a browser workflow and confirm an existing pending Cal booking when it meets your stated criteria.

View example

Confirm Ready Bookings from a Review Queue

On a schedule, use Airtop to review a booking queue and confirm eligible pending Cal bookings.

View example

Cancel a Booking after a Clear Request

Review a cancellation request in a browser workflow and cancel the matching active Cal booking when the request is clear.

View example

Decline a Pending Booking with a Review Reason

Review a booking request and decline it with a reason when it is pending and does not meet your stated criteria.

View example

Check Calendar Sync before Scheduling Review

Use Airtop to review a scheduling queue and check Cal's Google Calendar synchronization status before you rely on availability.

Supported Triggers and Actions

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

Airtop triggers

Cal actions

Recurring trigger

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

TriggerScheduled

Add member to team

Adds a new member to a team.

ActionInstant

Webhook trigger

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

TriggerInstant

Add attendee

Adds a new attendee to an existing booking.

ActionInstant

Add organization attribute option

Adds a new choice to an organization's single- or multiple-choice attribute.

ActionInstant

Delete oauth client webhook

Permanently deletes a webhook for an OAuth client, stopping its event notifications.

ActionInstant

Cancel booking via uid

Cancels an active booking using its unique identifier.

ActionInstant

Check calendar availability

Checks a calendar's free and busy times without revealing event details.

ActionInstant

Check gcal synchronization status

Checks the connection and sync status of a user's calendar integration.

ActionInstant

Check ics feed calendar endpoint

Checks whether a calendar feed is accessible and contains valid calendar data.

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.