Create Airtable records from Parsio parsed flat tables

Each document Parsio parses becomes a record in Airtable, with any table fields flattened into separate values, so extracted invoice, order or form data lands in a base you can sort and share.

Parsio

Airtable

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 1.2k sites Free to import

The Create Airtable records from Parsio parsed flat tables workflow on the FlowMattic canvas, with 2 steps across Parsio, Airtable — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Parsio pulls data out of emails and PDFs, but the results are most useful where your team already works with them. This workflow sends each parsed document into Airtable as a new record, so totals, dates, reference numbers and other extracted fields sit in a table you can filter, link and report on.

The Parsio Document Parsed (Flat Tables) trigger fires whenever a document is parsed in your mailbox. That includes new documents and older ones you parse again. If a document has table fields, such as invoice line items, Parsio flattens them into individual values instead of passing them as a list, which makes them easy to map into separate Airtable fields.

Nothing is mapped yet in the Airtable Create Record step: after import you pick the base and table and map Parsio's fields into your columns. Each run creates one record for the document, so a re-parsed document adds another record rather than replacing the first one.

Send a sample document through Parsio and check Task History to see exactly how the flattened fields are named before you map them.

Supplier invoices into an accounts base

A bookkeeper forwards supplier invoices to a Parsio mailbox, and each one becomes an Airtable record with the vendor, invoice number, date and total.

Order confirmations from marketplaces

An online seller parses order emails from several marketplaces and tracks them in one Airtable table for packing.

Lead emails turned into rows

A real estate office parses enquiry emails from property portals and reviews the extracted name, phone and listing in Airtable.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
Parsio Document Parsed ( Flat Tables )
Fires whenever Parsio parses a document, whether it is new or an older one parsed again. Table fields are flattened into separate values, ready to map one by one.
Step 2Action
Airtable Create Record
Creates one Airtable record per parsed document. No fields are mapped in the template, so choose your base and table, then map the Parsio values into the matching columns.

What you need

FlowMatticCore
Parsio AccountAccount
Airtable AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

Map a document identifier from the Parsio data, such as an ID or file name if your test run shows one, into its own Airtable field, so you can spot a second record from a re-parsed document.
If you need one Airtable record per table row, switch the trigger to Parsio's Document Parsed (Nested Tables) and add an Iterator over the table between the trigger and the Airtable step.
Set Airtable field types to match the data, such as currency for totals and date for invoice dates, so sorting and formulas work.

Questions about this workflow

Does re-parsing a document in Parsio create another Airtable record?

Yes. The trigger fires for new and old documents alike, and Create Record always adds a record. Re-parsing a document therefore gives you a second record for it.

How do invoice line items from Parsio appear in Airtable?

With this trigger, table fields are flattened into separate values for each row and column. You map the ones you need into Airtable fields; check a test document to see their names.

What about documents Parsio fails to parse?

A failed parse isn't a Document Parsed event, so this workflow stays idle. Parsio has a separate Document Parsed Failed trigger in FlowMattic if you want an alert for those.