Connect Abstract to Cal

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

View example

Check Cal availability from a meeting request

Review a meeting request, validate its contact details with Abstract, and check the requested calendar's availability in Cal.

View example

Review booking intake contacts

Use Abstract to validate booking contact details, then retrieve relevant Cal bookings for review.

View example

Confirm a requested Cal booking

Validate the requester email with Abstract, then confirm the specified eligible Cal booking by its UID.

View example

Decline a pending booking with a reason

Process a decline request, validate contact details with Abstract, and decline the identified pending Cal booking with an optional reason.

View example

Cancel a Cal booking from a verified request

Validate the requester's contact email with Abstract, then cancel the specified active Cal booking by UID.

View example

Get a daily review of upcoming Cal bookings

Retrieve upcoming Cal bookings on a schedule and use Abstract to summarize booking notes or supplied text for the run report.

View example

Check Cal Google Calendar sync on a schedule

Check whether a user's Google Calendar integration is connected and synchronized with Cal, then report the status.

View example

Check an ICS calendar feed before using it

Process an ICS feed request and have Cal check the feed URL's accessibility and calendar data integrity.

Supported Triggers and Actions

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

Abstract 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

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.