Connect Airtable to Basin

When something happens in Airtable, 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

Fires when a base's name or permission level changes.

Do this · Action

Creates a new form.

Build an automation Browse examples

Examples

Ways Notis can move work from Airtable to Basin

Turn Airtable schema changes into an updated intake form

When an Airtable base schema changes, review the update and create a Basin form for a newly needed intake flow.

Add a Basin webhook when a new Airtable view signals an integration need

Use a newly created Airtable view as a cue to create a Basin form webhook when you provide the form and callback details.

Review Basin webhook settings when an Airtable view is deleted

When a known Airtable view is deleted, review whether a related Basin webhook should be updated and apply a specified settings change.

Update a Basin integration when an Airtable view is renamed or retitled

Use an Airtable view name or type change to review a related Basin form integration and update it with specified settings.

Update a Basin project after an Airtable base metadata change

Use an Airtable base name or permission change to review a related Basin project's name and apply a specified rename when needed.

Review Basin submissions on a recurring schedule

On a schedule, retrieve submissions from a specified Basin form so Notis can summarize new entries and flag follow-up.

Supported Triggers and Actions

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

Airtable 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

Base Metadata Changed

Fires when a base's name or permission level changes.

TriggerPolling

Create Project

Creates a new project for organizing forms.

ActionInstant

Base Schema Changed

Fires when tables, fields, or views change in a base.

TriggerPolling

Delete Form

Permanently deletes a form; this action cannot be undone.

ActionInstant

User Profile Changed

Fires when the connected user's profile changes.

TriggerPolling

Delete Submission

Permanently deletes a form submission after its ID is confirmed.

ActionInstant

View Created

Fires when a new view is created in a base.

TriggerPolling

Delete Project

Deletes a Basin project by ID.

ActionInstant

View Deleted

Fires when a previously known view is deleted.

TriggerPolling

Delete Webhook

Deletes a form webhook.

ActionInstant

View Metadata Changed

Fires when a view's name or type changes.

TriggerPolling

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 schedule (recurring or one-time), and a change in one of your Notis databases.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,500+ 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

Scheduled triggers

Run a workflow on the clock, on a recurring schedule or once at a set date and time. Daily standups, hourly syncs, a one-off launch reminder: the workhorse of Notis.

Daily · 8:00Weekdays onlyOnce · Dec 13

Beta

Database triggers

Fire when a row in one of your Notis databases is added or edited, with optional filters on its properties. New lead added, status changed, value crosses a limit.

Row addedProperty editedValue > limit

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.