Skip to content

Airtable

Airtable records that write themselves from your email

Requests arriving by email become Airtable records — created or completed without duplicates, with the attachments in their field. And when a row changes in Airtable, a workflow can take it from there.

Connection
API key or token
Triggers
1
Actions
1
Turn a request into a record Hover a node to see its role · Drag to move the graph
Email receivedEmail receivedEmail receivedExtractExtractExtractModelAirtable — create or update — AirtableAirtable — create or…Airtable
Turn a request into a record

What you can automate with Airtable

Triggers

What starts a workflow.

Actions

What a workflow can do next.

  • Airtable

    Finds, creates, completes and comments rows in an Airtable base, and drops the attachments (from the email or added by a step) into it.

    Record
    • Search
    • Get a record
    • Create
    • Create or update
    • Update
    • Delete
    • Comment
    Attachment
    • Upload the attachments
    • List a record’s attachments
    • Fetch a record’s attachments into the run
    Base
    • Get a base schema
    • List the bases

Workflows you can build

Each one starts from a real situation and uses only nodes that exist today. Test it on past emails before you publish it.

  • Turn a request into a record

    The details are extracted and the record created, or completed if one already carries the same email address.

    1. Email received
    2. Extract
    3. Airtable — create or update
  • Attach the documents to the record

    The email’s attachments go straight into the record’s attachment field, never through a public URL.

    1. Email received
    2. Airtable — search
    3. Airtable — upload the attachments
  • Email the client when the status changes

    When a row moves to Accepted, a confirmation is drafted and sent from the mailbox you choose.

    1. Airtable row changed
    2. Condition (If)
    3. Compose (AI)
    4. Send

How to connect Airtable

Create a personal access token in Airtable, limited to the bases involved, and paste it into a new connection.

Before you start

  • An Airtable account with access to the bases to automate, and editor rights to write.
  • A personal access token, ideally created from a service account for a team.
  • For the trigger: a Last modified time field in the watched table.

The full guide in the documentation

  1. Sign in to Airtable, open airtable.com/create/tokens, then click “Create new token”.
  2. Give the token a clear name: it shows up in the record revision history (“Someone via <name>”).
  3. Under “Scopes”, add data.records:read, data.records:write and schema.bases:read — plus data.recordComments:write to post comments. The trigger polls the table: it needs no extra permission.
  4. Under “Access”, click “Add a base” and pick the bases involved: the token sees nothing else.
  5. Click “Create token” and copy it right away — Airtable shows it once — then paste it below and test the connection.
  6. The signing secret is only needed for Airtable webhooks: Airtable returns it once, when the webhook is created. Leave it empty otherwise.

Automate Airtable with Loop & Roll

We build the workflow around your processes, test it on your past emails and put it into service with your teams.