Plenty of business data still arrives by email: supplier quotes, lead alerts from listing portals, booking confirmations and shipping notices. FlowMattic's Email Parser gives you an address to forward them to, pulls out the sender, subject and body, and writes the details into an Airtable base where your team can sort, assign and track them.
3 triggers 7 actions 7 example workflows 2 ready-made templates Unlimited runs
When this happens in Email Parser2 triggers
Do this in Airtable7 actions
1. TriggerEmail Received2. ActionCreate RecordWhen Email Parser fires Email Received, FlowMattic runs Create Record in Airtable with the data from that event.
You build this in the FlowMattic workflow builder on your own site. See the setup steps
Each one uses only triggers and actions the two integrations ship today, plus FlowMattic's own tools. Where the library has a ready-made template, import it instead of building from scratch.
Ready-made templateQuotes forwarded to the parser address are saved with the supplier, subject and body, so procurement compares offers in one table instead of searching an inbox.
Email ReceivedCreate Record
View the template Property, directory and marketplace portals often send leads only as emails. A Filter keeps the ones from the portal's address and adds each enquiry to your leads table.
Email ReceivedFilterCreate Record
Free-form emails do not split into fields on their own. An AI Agent reads the body and returns the order number, amount and date as separate values for their own Airtable fields.
Email ReceivedAI AgentCreate Record
Invoices, booking confirmations and support requests can share one parser address. A Router reads the sender or subject and writes each email to the table it belongs in.
Email ReceivedRouterCreate Record
When a status email carries your Airtable record ID, for example in a reply subject, the matching record is updated with the new status and the date it changed.
Email ReceivedText FormatterUpdate Record
Date/Time Formatter turns the received date into the format your Airtable date field expects, so calendar and timeline views place each email on the right day.
Email ReceivedDate/Time FormatterCreate Record
Staff forward receipts to the parser address. Human in the Loop asks a manager to approve each one, and only approved receipts become records in the expenses table.
Email ReceivedHuman in the LoopCreate Record
When you finish, every email sent to your parser address is saved as a record in an Airtable table.
Create an Airtable table with fields such as Sender, Email, Subject, Body and Received.
Add an Airtable connection under Connects with access to the base you will use.
Create a workflow with the Email Parser Email Received trigger and copy the parser address it gives you.
Forward one real email to that address, or set your mailbox to forward matching emails, so FlowMattic captures the parsed fields.
Add an Airtable step with Create Record, pick the base and table, map the parsed fields, test it and switch the workflow on.
1. Trigger in Email Parser
Email Received
2. Action in Airtable
Create Record
Fields mapped from the earlier steps (a typical setup)
| From Email Parser | To Airtable |
|---|---|
| From name | Sender |
| From email | |
| Subject | Subject |
| Body | Body |
| Received date | Received |
A trigger starts a workflow. An action is something FlowMattic does in the app as a step.
Email Parser and Airtable connect through FlowMattic on your own site, with no separate automation account in the middle and no charge per run.
Emails that used to be read and retyped land in Airtable as fields your team can filter, assign and link to other records.
The Email Parser comes with FlowMattic, so there is no separate parsing service to sign up for before mail reaches Airtable.
Runs are unlimited on every plan, so a busy quote season or a flood of portal leads costs nothing extra.
FlowMattic gives your workflow an email address. Anything sent or forwarded there starts the workflow with the sender, subject and body as fields, and an Airtable step saves them as a new record or updates an existing one.
Yes. Add Text Formatter to pull a value out of the subject or body, or an AI Agent step that reads the email and returns the fields you ask for.
Yes. Forward each mailbox to the same parser address. A Router can still send different senders to different tables.
No. The parser address comes from the workflow. You only set your existing mailbox to forward the emails you want to process.
Yes, if the email carries the record ID. Extract it, then use Get Record to check it and Delete Record to remove it.
Did not find your answer? You can browse the help center or ask us directly.
Airtable and Slack44 shared templates
Airtable and Google Sheets8 shared templates
Airtable and Fluent Forms6 shared templates
Airtable and Telegram5 shared templates
Airtable and Discord5 shared templates
Airtable and Gmail5 shared templates
Airtable and AI Agents3 shared templates
Airtable and ClickUp3 shared templatesInstall FlowMattic, connect both accounts and import a template. Every run stays on your own server.
30-day money-back guarantee Unlimited workflows and runs Self-hosted
Reviewed 23 Oct 2026. The example workflows are written with AI from the real triggers and actions of both integrations and checked against them. Email Parser integration 1.0, Airtable integration 1.1.0.
