Forwarding email to Google Sheets is useful when you need a simple shared log rather than another inbox. Each message sent to a Mailsink address becomes one spreadsheet row that your team can filter, annotate, and report on.
This guide starts with a manual test. Once the row looks useful, you can add a narrow Gmail filter or Outlook rule.
What Mailsink saves to Google Sheets
Mailsink creates a spreadsheet with a standard set of columns:
| Column | What it contains |
|---|---|
| Date Received | The message date |
| Subject | The email subject |
| From | The sender |
| To, CC, BCC | Available recipient addresses |
| Email Text | The readable message body |
| Attachments | Available filenames and links |
| Message ID | The email message identifier |
Each forwarded email is appended as a new row. You can add your own workflow columns—such as Status, Owner, Notes, or Follow-up date—without changing the standard capture columns.
This is an email log, not an inbox replacement or a historical mailbox export. Start with new messages that have a clear job in the spreadsheet.
When Google Sheets is the right destination
Choose Sheets when the workflow is lightweight and familiar:
- a shared log of inquiries or requests;
- receipt or invoice intake for later review;
- a newsletter or notification register;
- a small operations queue;
- data that will be filtered, exported, or summarized with formulas.
Choose Airtable when you need a stronger operational database with typed fields and workflow views. Choose Notion when the saved message belongs beside pages, notes, or project context.
Step 1: connect your Google account
- Create a Mailsink account.
- Open Connections and connect Google.
- Review Google's authorization screen and allow the access needed to create and update the destination spreadsheet.
- Return to Mailsink when authorization finishes.
Only connect the Google account that should own the spreadsheet. If your organization limits third-party apps, an administrator may need to approve the connection.
Step 2: create a Google Sheets inbox
- Open Inboxes and choose Create.
- Select Custom Setup as the workflow.
- Select Google Sheets as the destination.
- Choose the connected Google account.
- Optionally name the spreadsheet, then create the inbox.
- Copy the private address ending in @in.mailsink.app.
Mailsink creates a new spreadsheet in Google Drive and shows a link to it. Use one inbox and spreadsheet for one clear workflow so the rows remain understandable.
Step 3: forward one real email manually
Before configuring automation, forward one representative message to the generated Mailsink address. Then open the spreadsheet and inspect the new row.
Check that:
- the subject and sender are correct;
- the body is readable enough for the workflow;
- recipient fields contain what you expect after forwarding;
- an attachment you care about has a usable filename and link;
- the row does not expose information to people who should not see it.
If the test fails, check the Mailsink activity state, Google connection, spreadsheet permissions, and account limits before changing a provider rule.
Step 4: add selective forwarding
Manual forwarding may be enough for messages selected by a person. If you need automatic capture, start with the smallest useful rule.
Gmail
Google requires a forwarding address to be verified before automatic forwarding can start. The current Mailsink beta does not reliably surface that verification message in-app, so manual forwarding or BCC is the dependable starting path.
If you can complete the verification flow, follow Google's current forwarding instructions and create a filter for a narrow sender, recipient, or subject pattern. Do not forward the entire mailbox merely to test the integration.
Outlook and Microsoft 365
Create a rule for the specific messages you want to log. Some Microsoft 365 tenants block automatic external forwarding; Microsoft documents this as an organization-controlled policy and may return a 5.7.520 response. Use an administrator-approved route or manual forwarding when necessary.
See Microsoft's external forwarding policy for the current constraint.
Practical Google Sheets workflows
Inquiry tracker
Forward messages sent to a sales or contact address. Add Owner, Status, and Next action columns, then filter for rows that still need a response.
Support intake log
Capture selected support messages and add Assigned to, Priority, and Resolved columns. A spreadsheet is suitable for a small queue; use a dedicated ticketing system when routing, permissions, or service-level reporting becomes complex.
Receipt review
Send receipts to a dedicated sheet, then add and manually verify Vendor, Amount, Category, and Reviewed. The source email remains the authority for financial data.
Notification register
Log recurring service notifications or reports, then use filters and formulas to spot missing dates, repeated senders, or messages that require action.
Keep the sheet useful
- Create separate inboxes for unrelated workflows.
- Keep the forwarding rule narrower than the spreadsheet's purpose.
- Protect the sheet with appropriate Google sharing permissions.
- Review attachment links and retention needs before using sensitive messages.
- Keep business-critical values subject to human review.
- Archive or split very large sheets when they become difficult to operate.
Common questions
Can Mailsink write to an existing spreadsheet?
The current Google Sheets setup creates a new spreadsheet for the inbox. You can add workflow columns to that sheet after creation.
Can I customize the standard columns?
You can add columns for your own process. Keep the standard capture columns in place so incoming rows continue to match the generated structure.
Where are attachments stored?
The Attachments cell contains available filenames and links produced by the configured Mailsink workflow. Test the file types and access permissions that matter to you before relying on them.
Can multiple email accounts feed one sheet?
Yes, when each provider is allowed to send or forward to the same Mailsink address. Use separate inboxes when the messages need different permissions or workflows.
Start with one row
The useful milestone is one representative email becoming a complete, understandable spreadsheet row. Prove that first; automate the provider route second.
Create a Google Sheets inbox →
If preserving the original message file matters more than structured rows, use the email-to-Google-Drive guide.
Last updated: September 1, 2026