How to Set Up Airtable Email Automations (Send Emails from Your Base)

Email is the most common automation Airtable users build, and the one with the highest immediate ROI. The team gets time back the day you stop manually sending confirmations, reminders, and status updates.

This guide covers every option: native email actions, Gmail and Outlook integrations, SendGrid for transactional bulk sends, dynamic templates, button-triggered emails, and the drip-sequence pattern.

The Four Email Pathways

Airtable email automation breaks into four distinct pathways. Each fits a different job:

Most automation stacks use two or three of these depending on the message type.

Pathway 1: Native Send Email Action

The default option, available on every Airtable plan that includes automations.

Setup

1. Open Automations, click + Create automation.
2. Trigger: When record matches conditions (recommended over "record created" to avoid firing on half-filled records).
3. Action: Send email.
4. Configure:
   • To: an email field on the triggering record.
   • Subject: a templated string with {Field Name} references.
   • Message: HTML or plain text with field references.
   • Attachments: optional, reference any Airtable attachment field.
5. Save and turn on.

What's good and bad

Good: Free, instant, works on every plan, supports HTML and attachments.

Bad: Sends from no-reply@airtableemail.com — recipients see an Airtable-branded address. Reply-to can be set to your address, but the From address remains Airtable's. Use this for internal team notifications, not client communications.

Pathway 2: Gmail and Outlook Actions

Send from your real inbox. Authenticate the Gmail or Outlook account inside the automation action.

When to use

• Client-facing 1:1 emails (proposal sent, contract signed, follow-up).
• Personalized status updates that benefit from coming from a real person.
• Emails that need to thread with existing conversations in your inbox.

Setup mirrors the native action

Same trigger structure; replace the Send Email action with Send Gmail email or Send Outlook email. First-time use prompts OAuth authentication.

Important caveats

• Sender token expires. If the authenticating user changes their password, leaves the company, or revokes the app, every dependent automation breaks. Use a dedicated "automation" Gmail account (e.g. notifications@yourcompany.com) instead of a real user's account.
• Daily sending limits. Gmail caps at 500 sends/day per individual account and 2,000/day per Workspace account. Outlook caps at 10,000 recipients/day per mailbox. Exceeding these gets the account temporarily suspended.
• Avoid bulk patterns. Gmail flags accounts that send to many distinct recipients with similar bodies — looks like spam. Bulk sends should go through SendGrid.

For deeper Outlook integration patterns, see our Outlook and Office 365 integration guide.

Pathway 3: SendGrid for Transactional Bulk

For invoices, password resets, order confirmations, weekly digests at scale, transactional email services are the right tool.

Why SendGrid (or Mailgun, Postmark)

• Built for high volume — 100K+ emails/day on entry plans.
• Excellent deliverability (dedicated IP, DKIM, SPF properly handled).
• Detailed delivery analytics — opens, clicks, bounces, spam complaints.
• Webhook events back to Airtable for closed-loop tracking.

Setup with Make

1. Trigger: Airtable webhook fired from an automation, or scheduled run.
2. Action: SendGrid Send Email — supports HTML, plain text, dynamic templates with handlebars syntax, and attachments.
3. Write back: Update the Airtable record's Email Sent At and Send Grid Message ID fields.
4. Webhook back: Configure SendGrid event webhook to a Make scenario that updates the Airtable record on delivery, open, click, bounce, or unsubscribe events.

For an end-to-end Airtable email pipeline, see our Mailchimp integration guide — the same architecture patterns apply.

Pathway 4: Dynamic Templates with Field References

Whatever pathway you use, the template is where the email gets personalized.

Inline templating (native action)

Reference any field with {Field Name}. Handles most cases:

Hi {First Name},

Your order #{Order Number} for ${Total} has been confirmed.

Expected delivery: {Delivery Date}.

Reply to this email with any questions.

Best,
The {Company} team

Formula-built templates

For more complex logic (conditional sections, formatted dates, calculated greetings), build a formula field that produces the email body, then reference that single field in the email action.

"Hi " & {First Name} & ",\n\n" & 
IF({Order Total} > 1000, 
  "Thanks for your large order! ",
  "Thanks for your order! "
) & 
"Your order #" & {Order Number} & " for $" & {Total} & 
" has been confirmed.\n\nExpected delivery: " & 
DATETIME_FORMAT({Delivery Date}, 'MMMM D, YYYY') & "."

See our Airtable formulas cheat sheet for the syntax.

SendGrid Dynamic Templates

For the cleanest separation between data and template, use SendGrid's Dynamic Templates. The template lives in SendGrid (designed in a WYSIWYG editor), and your Make scenario passes a JSON payload of variables. SendGrid handles the merge.

This is the right architecture for any email that's going to be edited by marketing or content teams — they edit the template in SendGrid without touching Airtable or Make.

Button-Triggered Emails

A common pattern: the user clicks a button on a row to send a personalized email on demand (approval, reminder, follow-up).

Setup

1. Add a Button field to your table.
2. Set the button's action to Run Automation.
3. Create an automation with the When a button is clicked trigger, pointed at the button field.
4. Add your email-send action below.
5. Save and turn on.

Now clicking the button on any row sends a personalized email with that row's data. This pattern is especially useful for:

• Sending approval notifications when the approver is ready (not on every record update).
• Triggering follow-up emails on a schedule the team controls manually.
• Re-sending an email after fixing the recipient's address or attachment.

For more button patterns, see our Airtable buttons guide.

Drip Sequence Pattern

For multi-step email sequences (onboarding, nurture, re-engagement), the pattern uses a Sequences table.

Schema

Automation per step

For each step, create a scheduled automation:

• Trigger: Run hourly.
• Find records: Status = "Active" AND Step N Send Date <= NOW() AND Step N Sent = false.
• For each record: Send the email for Step N.
• Update: Step N Sent = true.

Repeat for every step in the sequence.

When to graduate

Airtable handles drip sequences up to about 5–7 steps and 1,000 active recipients. Beyond that, use a dedicated tool: Mailchimp Journeys, Customer.io, ConvertKit, or HubSpot Workflows. They handle the queue management, A/B testing, and analytics better than Airtable can.

Comparison: Email Pathway Decision Matrix

Common Mistakes

Mistake 1: Sending from Gmail to large audiences. Gmail will throttle or suspend the account. Bulk sends belong in SendGrid or a marketing platform.

Mistake 2: Using "when record created" instead of "matches conditions." Records often get created in a half-filled state. The automation fires on every new record, sending half-empty emails.

Mistake 3: Not testing emails before turning automations on. Send a test to yourself first. Field references silently fail when fields are empty, producing {Field Name} literally in the email body.

Mistake 4: Forgetting unsubscribe handling. For any email that isn't strictly transactional, you need an unsubscribe link and a process to honor opt-outs. SendGrid handles this; native and Gmail don't.

Mistake 5: HTML email that doesn't render in Outlook. Outlook's rendering engine is decades behind every other client. Test HTML emails in Outlook specifically; avoid CSS features that don't work there.

Troubleshooting

Email shows {Field Name} literally in the body. The field is empty on the triggering record, or the field name has a typo. Field references are case-sensitive.

Gmail action fails with "Insufficient Permission." The authenticated user's OAuth scopes were revoked or the account was disabled. Re-authenticate.

SendGrid sends successfully but recipients don't get the email. Check the SendGrid Activity feed — most likely a spam-folder delivery or a bounce. Verify DKIM and SPF records are set up on your sending domain.

Attachments not appearing on the email. The attachment field is empty on the triggering record, or the file is too large (Gmail caps at 25MB total).

Drip sequence stops mid-sequence. A scheduled automation hit an error and disabled itself. Open Automations and look for any with the "errored" badge. Fix the underlying issue, then re-enable.

Next Steps

Email automation is the on-ramp to a wider automation practice. Once a few sends are running reliably, the next steps are usually adding email-driven workflows (parse inbound replies, route based on response), building approval flows that depend on email confirmations, and connecting email engagement back to lead scoring or customer health metrics.

For more patterns, see our Airtable automation guide, Make automation guide, and mail merge guide. For client-facing email programs at scale, get in touch — we design these regularly.