Outlook to Airtable: 4 Ways to Connect Outlook and Airtable

Search "outlook airtable integration" and you get a wall of Power Automate tutorials, then a wall of Zapier templates. Both work. Both are also more machinery than most people need to move an email into a table.

I build Quicktion, which does Outlook to Airtable through forwarding, so keep that in mind while you read. What I want to do here is lay out the four ways this actually gets done in 2026 and be straight about where each one is the right call, including the two where I'm not involved at all.

The four methods:

1. Email forwarding with an Outlook rule (Quicktion)
2. Microsoft Power Automate
3. Zapier or Make
4. Airtable's own "When email received" trigger

One thing up front, since it's the most common question I get from Outlook users: there is no Quicktion Outlook add-in. The Gmail add-on doesn't run in Outlook. Everything below for method 1 goes through forwarding, and forwarding is enough for most of the workflows people bring me.

Method 1: Email forwarding with an Outlook rule (Quicktion)

The shape is simple. Outlook already knows how to forward mail. Airtable already accepts records through its API. Quicktion sits in the middle and turns one into the other.

How it works

You connect your Airtable account in Quicktion, pick a base and a table, and map the parts of an email to fields: subject to a Single Line Text, sender to an Email field, date to a Date field, body to a Long Text, attachments to a Multiple Attachments field. Quicktion then gives you a forwarding address like xyz@in.quicktion.io for that destination.

In Outlook you create a rule: from a client domain, or subject contains "invoice", or sent to your shared support mailbox. Action: forward to your Quicktion address. Every email that matches becomes an Airtable record a few seconds later.

That's the whole integration. No flow editor, no field mapping in JSON, nothing to redeploy when someone renames a column.

The Outlook-specific bits worth knowing

Rules created in Outlook on the web (or in the Exchange admin center) run on the server. Your laptop can be closed. Rules created only in the Windows desktop client run when Outlook is open, so if you need 24/7 intake, build the rule on the web side.

Shared mailboxes work the same way. Put the rule on sales@ or support@ and every teammate sees the records in the shared table.

Some tenants block external auto-forwarding through Exchange transport rules. If your rule saves but nothing arrives, that's the first thing to check with IT.

Outlook categories don't survive forwarding. Use Quicktion's default values instead: set Source = "Outlook" or Status = "New" on the destination and every record lands tagged.

The full click-by-click walkthrough for desktop, web, and Exchange rules is in How to Save Outlook Emails to Airtable. I'm not going to repeat it here.

What you get

Body converted from HTML to markdown, so links stay clickable and the Long Text field doesn't fill with <div> soup. Attachments uploaded straight into the Multiple Attachments field, as real Airtable files rather than links to somewhere else. On Pro, AI Email Intelligence reads the body and any PDF or image attachment and fills fields you define: invoice total, vendor, priority, whatever your prompt asks for.

What you don't get

No edit-before-save. That's the one real thing Gmail users have that Outlook users don't, because it lives in the add-on. Records are mapped from the destination config, which is fine for predictable intake and less fine for "I want to tweak the Company field on this one email before it lands." Quicktion also won't look up an existing contact and link the record to it; you can default a Linked Record field, but dynamic lookups belong in an Airtable Automation on top of the table.

When to use it

When the job really is "this kind of email should become a record in this table." Client correspondence into a CRM, invoices into an expenses base, support mail into a tickets table, form notifications into a leads table. If that's you, this is the fastest and cheapest path, and it doesn't care whether you're on Outlook desktop, web, mobile, Microsoft 365, or an on-prem Exchange that forwards externally.

Free covers 25 emails a month and one destination. Pro is $12/month for 1,000 emails and unlimited destinations.

Method 2: Microsoft Power Automate

If your organization lives in the Microsoft tenant, Power Automate is the tool your IT team will point you at, and it's a real option.

How it works

Trigger: "When a new email arrives (V3)" from the Office 365 Outlook connector, optionally filtered by folder, sender, or subject. Action: "Create a record" from the Airtable connector. Between them you'll usually add steps to convert the HTML body to text, loop over attachments, and write them somewhere (OneDrive or SharePoint) so you have a URL to hand to Airtable.

The licensing catch

The Airtable connector is a Premium connector. Microsoft's own connector reference also lists it as an Independent Publisher connector, marked deprecated, authenticating with an API key. A standard Microsoft 365 seat gets you Standard connectors only, so to use it you need Power Automate Premium licensing, per user or per flow.

The Outlook trigger is Standard. It's the Airtable end that pushes you into Premium.

Where it gets tedious

Attachments come into Power Automate as Base64 content, and the Airtable action wants a URL. So the standard pattern is a loop that writes each file to SharePoint or OneDrive, grabs a sharing link, and passes that in. It works, and it means your Airtable attachments are SharePoint links governed by SharePoint sharing policy, not files in Airtable. Field references are by name, so a renamed column silently breaks the flow at the next run. And AI extraction means AI Builder, which is its own credit pack.

I wrote the long version of this in Outlook to Airtable Without Power Automate.

When to use it

When you already run Power Automate flows for other Microsoft 365 work, already have Premium licensing, and the Airtable step is one piece of a longer flow that also touches Teams, SharePoint, or Dynamics. Or when your compliance team has standardized on Power Platform audit logs and DLP policies and a third-party forwarding tool isn't going to get through review. Both are legitimate. For a standalone "email to Airtable record" job it's more than you need.

Method 3: Zapier or Make

Both platforms have a Microsoft Outlook trigger and an Airtable action, and both have templates for exactly this.

How it works

Zapier: trigger "New Email" (or "New Flagged Email", or "New Attachment") in Microsoft Outlook, action "Create Record" in Airtable. Make: a Microsoft 365 Email "Watch Messages" module feeding an Airtable "Create a Record" module.

Where they fall short for Airtable specifically

The email body arrives as plain text or raw HTML, and there's no built-in "make this readable markdown" step. Attachments come through as file objects you have to route into a Multiple Attachments field yourself, usually with an extra step or two. Triggers poll on an interval rather than firing when the mail lands, so there's a delay. And every email is a task or an operation, so a busy shared inbox eats through the free tier fast and turns into a per-email bill.

When to use them

When the Outlook email needs to fan out. Create the Airtable record and post to Slack and add a row in Sheets and ping a Teams channel, in one automation. If Airtable is the only endpoint, you'll pay more and get messier records than with forwarding. If you're comparing against Zapier specifically, Zapier Email to Airtable Alternative goes deeper.

Method 4: Airtable's own "When email received" trigger

This is the one people forget exists, and it deserves an honest look because it's the only option that lives entirely inside Airtable.

How it works

In Airtable Automations, pick the "When email received" trigger. Airtable generates an inbound address for that automation. Point an Outlook rule at it and the trigger fires with the email's fields, which you map into a "Create record" action.

The limits, per Airtable's own docs

Three things from Airtable's support page for the trigger matter here.

Plan availability: it's listed for Business and Enterprise Scale plans only. If you're on Free or Team, you don't have it.

Attachments: they arrive as an expiringDownloadUrl that stays valid for two hours after the email is received. Write that URL into an attachment field in the same automation run and Airtable re-hosts the file, which is fine. Stash it anywhere else and you'll have a dead link by lunch.

Forwarding: Airtable warns that when mail reaches the automation address through a forwarding rule, the trigger may not fire even though the email was delivered, because forwarded messages tend to fail SPF checks. Their fix is to add the address as a direct To/CC/BCC recipient instead of forwarding. That works for mail you send, and doesn't help with mail that was already sent to you, which is most of what people are trying to capture. There's also a 30 MB size cap including attachments.

When to use it

When you're on a plan that includes it, your intake mail is coming from a system you control (a form tool, a notification service) where you can put the automation address directly in the To field, and you're comfortable mapping the attachment URL inside the run. In that specific setup it's free and native. For "forward my Outlook client mail into a table" it's the shakiest of the four.

The wider comparison, including the Gmail trigger, is in Airtable Automations vs Quicktion.

Method comparison

Which one should you actually pick

If Airtable is where the email needs to end up and that's the whole job, use forwarding. It's the only one of the four that was built for exactly this, the records come out clean, and it costs nothing to try.

If you're inside a Microsoft shop with Premium licensing and a Power Platform team, and the Airtable record is one step in a bigger flow, stay in Power Automate. You already paid for it and your admins can see it.

If the email has to land in three places at once, Zapier or Make.

If you're on Airtable Business or Enterprise Scale and the mail comes from a system where you can set the recipient directly, the native trigger is free and worth a try, with the two-hour attachment window in mind.

Getting started

Sign up for Quicktion, connect Airtable, create a destination, and set one Outlook rule. Forward a test email and check that the body reads well in the Long Text field and the attachment landed where you expected. Free is 25 emails a month, which is enough to find out.

Related guides

• How to Save Outlook Emails to Airtable, the step-by-step for Outlook desktop, web, Exchange rules, and shared mailboxes
• Outlook to Airtable Without Power Automate, the long version of the Power Automate section
• Airtable Automations vs Quicktion, the native trigger in depth
• Gmail to Airtable Integration, if part of your team is on Gmail
• Outlook to Airtable, the product page