Mailparser already turns order notices, lead emails and reports into fields. FlowMattic takes those fields and puts them in Google Sheets: one row per email, one row per line item, or an update to a row you already have. It suits operations and sales teams who keep their working lists in a spreadsheet.
8 triggers19 actions6 example workflows1 ready-made templateUnlimited runs
Try a pairing
When this happens in Mailparser2 triggers
Do this in Google Sheets19 actions
1. TriggerNew Email Parsed (Per Email)
2. ActionAdd New Row
When Mailparser fires New Email Parsed (Per Email), FlowMattic runs Add New Row in Google Sheets with the data from that event.
You build this in the FlowMattic workflow builder on your own site. See the setup steps
Mailparser and Google Sheets workflows you can build
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 template
Add a row for each email Mailparser parses
Every parsed lead, order or booking email becomes one row with the fields your parsing rules extracted, so the sheet is the list the team works from.
Write every line item of an order email as its own row
When a parsing rule returns a table, the Per Row trigger fires once for each line. A stock or picking sheet then gets one row per product, not a bundled cell.
New Email Parsed (Per Row)→Add New Row
Update the order row when the shipping email arrives
Look up the order number from the parsed shipping notice and write the carrier and tracking number into the row the order email created earlier.
New Email Parsed (Per Email)→Lookup Row Data→Update Row
Send each Mailparser inbox to its own tab
Leads, invoices and supplier updates often go to different Mailparser inboxes. A Router writes each kind to its own tab in one shared spreadsheet.
New Email Parsed (Per Email)→Router→Add New Row
Fix dates and amounts before they reach the sheet
Emails write dates and prices in many formats. Format them first so the sheet can sort by date and add up totals without manual clean-up.
New Email Parsed (Per Email)→Date/Time Formatter→Number Formatter→Add New Row
Skip emails the parsing rules could not read
A Filter stops the workflow when a key field such as the order number is empty, so half-parsed emails do not leave blank rows for someone to chase.
New Email Parsed (Per Email)→Filter→Add New Row
Set up: one row per parsed email
At the end, every email parsed in your Mailparser inbox adds a row to your Google Sheet.
1
Finish the parsing rules
In Mailparser, set up the inbox and its parsing rules first, so each email already produces the fields you want in the sheet.
2
Connect both apps
In FlowMattic, open Connects and add Mailparser and a Google account that can edit the spreadsheet.
3
Start with New Email Parsed (Per Email)
Create a workflow, choose Mailparser and the Per Email trigger, select the inbox and send a test email so the parsed fields are captured.
4
Add New Row
Add Google Sheets with Add New Row, choose the spreadsheet and tab, map the parsed fields to the columns, test and switch the workflow on.
Add a row for each email Mailparser parsesTemplate
1. Trigger in Mailparser
New Email Parsed (Per Email)
2. Action in Google Sheets
Add New Row
Fields mapped from the earlier steps (a typical setup)
From Mailparser
To Google Sheets
Received date
Date
Sender
From
Order number
Order
Customer name
Customer
Total
Amount
Built on the FlowMattic canvas. Test each step with real data, then switch the workflow on.
Triggers and actions in this pair
A trigger starts a workflow. An action is something FlowMattic does in the app as a step.
Good to know
Mailparser has triggers only, so these workflows start when Mailparser parses an email. Google Sheets triggers cannot send data back into Mailparser.
The Per Row trigger repeats the email-level fields on every line item, so pick Per Email when you want exactly one row per message.
The mapped fields come from your own parsing rules, so the mapping above is an example. Changing a rule can change the field names the workflow receives.
New Spreadsheet RowTrigger when a new row is added to the spreadsheet
New Or Updated Spreadsheet RowTrigger when a row is updated in the spreadsheet
Deleted Spreadsheet RowTrigger when a row is deleted from the spreadsheet
Update Cell DataTrigger when any cell is updated in the spreadsheet
Update Specific Cell DataTrigger when a specific cell is updated in the spreadsheet
Update Specific Column ValueTrigger when a specific column value is updated in the spreadsheet
Actions (19)
Add New RowAdd a new row with mapped data
Update RowUpdate existing row in specific spreadsheet with mapped data
Delete RowDelete row by ID in specific spreadsheet
Clear Row DataClear data or row by ID in specific spreadsheet
Lookup Row DataSearch for data in specific spreadsheet
Get Cell DataGet data for particular cell in specific spreadsheet
Update Cell DataUpdate data for particular cell in specific spreadsheet
Get Row CountGet total number of rows in specific spreadsheet
Get Row DataGet rows data from the sheet based on specified range
Create Spreadsheet ColumnCreate a new column in specific spreadsheet
Create New SheetCreate a new sheet in specific spreadsheet
Import CSV or JSON to Existing SheetImport CSV or JSON data to existing sheet in specific spreadsheet
Copy SheetCopy a sheet to another or within the same spreadsheet
Get RowsRetrieve rows in JSON format for use with Iterator
Export sheet to CSVExport the selected sheet to CSV format and save to WordPress Media Library
Export Sheet to ExcelExport the spreadsheet to Excel (.xlsx) format and save to WordPress Media Library
Export Sheet to PDFExport the spreadsheet to PDF format and save to WordPress Media Library
Export Sheet to OpenDocumentExport the spreadsheet to OpenDocument (.ods) format and save to WordPress Media Library
Export Sheet to TSVExport the selected sheet to TSV format and save to WordPress Media Library
Why run this pair with FlowMattic
Mailparser and Google Sheets connect through FlowMattic on your own site, with no separate automation account in the middle and no charge per run.
Parsed data lands in a list people use
Fields from Mailparser go straight into the spreadsheet your team already sorts, filters and shares.
Order emails stay on your server
After Mailparser extracts the fields, the workflow runs on your own WordPress site, not in another company's automation account.
Busy inboxes cost the same
Runs are unlimited, so a thousand parsed order emails in a sale week need no bigger plan than ten.
Common questions
Should I use the Per Row or Per Email trigger?
Use Per Email when one email is one record, such as a lead. Use Per Row when the email holds a table, such as an order with several products, and you want each line on its own row.
Can I update rows instead of adding new ones?
Yes. Search the sheet with Lookup Row Data using a parsed value like an order number, then run Update Row on the row it finds.
Do I need to change my Mailparser rules?
No. FlowMattic receives whatever fields your rules produce. If you add a rule later, send a new test email so the new field appears for mapping.
Can one parsed email go to two spreadsheets?
Yes. Add a second Add New Row step for the other spreadsheet, or use a Router so only some emails reach it.
30-day money-back guarantee Unlimited workflows and runs Self-hosted
Reviewed 27 Oct 2026. The example workflows are written with AI from the real triggers and actions of both integrations and checked against them. Mailparser integration 1.0, Google Sheets integration 2.2.4.