Connect Airtable to Ashby

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

Add a candidate to a recruiting project.

Build an automation Browse examples

Examples

Ways Notis can move work from Airtable to Ashby

Turn Airtable Hiring Reviews into Ashby Notes

Send an Airtable hiring review to Notis and add its decision context to the matching Ashby candidate profile.

Label Ashby Candidates from an Airtable Shortlist

Use a Notis webhook to add an existing Ashby tag to candidates selected for a sourcing shortlist in Airtable.

Refresh Ashby Candidate Notes from Airtable Pipeline Reviews

On a schedule, review Airtable pipeline context and add a concise update to matching Ashby candidate profiles.

Mirror Approved Airtable Hiring Fields in Ashby

When Airtable schema changes, use Notis to review approved hiring field changes and create corresponding Ashby custom fields.

Route New Airtable Sourcing Views to Ashby Projects

When a sourcing view is created, have Notis add explicitly identified candidates to the corresponding Ashby sourcing project.

Update Ashby Candidate Labels When Airtable Views Change

When an Airtable view's metadata changes, apply an explicitly specified existing Ashby tag to the affected candidates.

Supported Triggers and Actions

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

Airtable triggers

Ashby actions

Recurring trigger

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

TriggerScheduled

Add Candidate to Project

Add a candidate to a recruiting project.

ActionInstant

Webhook trigger

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

TriggerInstant

Add Candidate Tag

Add an existing tag to a candidate’s profile.

ActionInstant

Base Metadata Changed

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

TriggerPolling

Add Hiring Team Member

Assign a team member to a hiring team.

ActionInstant

Base Schema Changed

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

TriggerPolling

Add Completed Assessment to Candidate

Adds a completed partner assessment to an Ashby candidate; requires candidatesWrite permission.

ActionInstant

User Profile Changed

Fires when the connected user's profile changes.

TriggerPolling

Add User to Interviewer Pool

Add a user to a pool of interviewers.

ActionInstant

View Created

Fires when a new view is created in a base.

TriggerPolling

Add Existing Email Message to Candidate

Attaches an existing partner email to an Ashby candidate without sending it; requires candidatesWrite permission.

ActionInstant

View Deleted

Fires when a previously known view is deleted.

TriggerPolling

Add Opening Job

Link an existing job to a job requisition.

ActionInstant

View Metadata Changed

Fires when a view's name or type changes.

TriggerPolling

Add Opening Location

Associate a location with an existing job requisition.

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.