Connect Abstract to Basin

When something happens in Abstract, Notis takes the next step in Basin. 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 Basin

View example

Create Basin forms from validated requests

Check incoming form requests with Abstract, then create a Basin form when the request includes the details needed to set it up.

View example

Create Basin projects for qualified lead campaigns

Use Abstract to inspect incoming campaign requests, then create a Basin project when the request clearly calls for a new organizational container.

View example

Add Basin form callbacks from verified requests

Check incoming integration requests, then add a Basin form webhook when the request includes a form ID and confirmed callback URL.

View example

Forward Basin submissions to a notification endpoint

When a webhook request supplies a form ID and an external destination, create a Basin notification webhook to forward form submissions there.

View example

Review Basin submissions on a schedule

Fetch submissions for a specified Basin form on a recurring schedule, then use Abstract to process available text for a concise review.

View example

Check Basin form webhook configurations

On a schedule, retrieve webhooks for a specified Basin form and use Abstract to process the configuration details into a readable check-in.

View example

Keep a scheduled inventory of Basin forms

Fetch the Basin forms list on a recurring schedule and use Abstract to process the returned information into a concise inventory report.

View example

Review Basin projects on a schedule

Retrieve Basin's project list on a recurring schedule and process the returned details into a short report for your team.

View example

Check Basin domains from an incoming request

Use a webhook request to start a Notis run that retrieves Basin's configured domains and processes the results for a clear response.

Supported Triggers and Actions

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

Abstract triggers

Basin actions

Recurring trigger

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

TriggerScheduled

Create Form

Creates a new form.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Form Webhook

Creates a webhook for a form.

ActionInstant

Create Project

Creates a new project for organizing forms.

ActionInstant

Delete Form

Permanently deletes a form; this action cannot be undone.

ActionInstant

Delete Submission

ActionInstant

Delete Project

Deletes a project.

ActionInstant

Delete Webhook

Deletes a form webhook.

ActionInstant

Get Domains

Lists the custom domains linked to your account.

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.