Connect Airtable to Bigmailer

When something happens in Airtable, Notis takes the next step in Bigmailer. 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 transactional email campaign for a brand.

Build an automation Browse examples

Examples

Ways Notis can move work from Airtable to Bigmailer

Alert on Airtable access changes

Create a Bigmailer transactional campaign when an Airtable base name or permission level changes, so the change reaches the designated operations recipient.

Brief the team on Airtable schema changes

Turn Airtable table, field, or view structure changes into a concise Bigmailer transactional campaign for a team contact you specify.

Notify on deleted Airtable views

Create a Bigmailer transactional campaign when a known Airtable view is deleted, so a designated teammate can check dependent workflows.

Review newly created Airtable views

Create a Bigmailer transactional campaign when a new Airtable view is created, prompting a designated owner to review its purpose and access.

Check Bigmailer after Airtable profile changes

When the connected Airtable user's profile changes, retrieve Bigmailer user information to confirm the target connection remains accessible.

Supported Triggers and Actions

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

Airtable triggers

Bigmailer actions

Recurring trigger

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

TriggerScheduled

Create Transactional Campaign

Creates a transactional email campaign for a brand.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Brand

Creates a brand for organizing campaigns and default sending settings.

ActionInstant

Base Metadata Changed

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

TriggerPolling

Get User Information

Retrieves information about the authenticated user.

ActionInstant

Base Schema Changed

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

TriggerPolling

Create Brand Property

Creates a custom brand property for use in email templates.

ActionInstant

User Profile Changed

Fires when the connected user's profile changes.

TriggerPolling

List All Brands

Lists brands in the authenticated BigMailer account.

ActionInstant

View Created

Fires when a new view is created in a base.

TriggerPolling

Create Bulk Campaign

Creates a bulk email campaign for immediate sending or scheduling.

ActionInstant

View Deleted

Fires when a previously known view is deleted.

TriggerPolling

Create Contact

Creates a contact within a brand, with optional list membership and subscription status.

ActionInstant

View Metadata Changed

Fires when a view's name or type changes.

TriggerPolling

Create Contact Batch

Uploads 1 to 1,000 contacts for asynchronous creation or update in a BigMailer brand.

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.