> ## Documentation Index
> Fetch the complete documentation index at: https://docs.newie.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Newie + Google Sheets

> Connect Newie with Google Sheets through Zapier.

## Overview

Google Sheets is the simplest place to keep a running Newie event log. It gives operators a filterable record of customers, payments, invoices, and lifecycle changes without setting up a heavier reporting tool.

## What You'll Need

* Newie connected to Zapier
* A Google account with access to the target spreadsheet
* A spreadsheet with column headers already in place; Zapier maps to existing headers, so create them before building the Zap

## Common Zaps

**Subscription Started → Google Sheets: Create Spreadsheet Row**

Append a row to a "Customers" sheet with name, email, service, and active start date when billing starts and the subscription becomes active.

**Payment Paid → Google Sheets: Create Spreadsheet Row**

Append a row to a "Payments" sheet for every successful payment - useful for monthly revenue snapshots and cross-checks against your accounting tool. For BECS Direct Debit, this row is created after bank confirmation, not at initial payment submission.

**Payment Overdue → Google Sheets: Create Spreadsheet Row**

Log overdue invoices to a dedicated tab so someone can work the list daily.

**Subscription Ends → Google Sheets: Update Spreadsheet Row**

Use Lookup Spreadsheet Row first to find the customer in the Customers sheet, then update an "End Date" column so the row reflects current status.

## Setup at a Glance

1. If you have not connected Newie yet, follow [Connecting Newie to Zapier](/integrations#connecting-newie-to-zapier) first.
2. In Zapier, create a new Zap and choose Newie as the trigger. Pick the trigger event (e.g. Payment Paid, Subscription Started, or One-Off Purchase Complete).
3. Connect Google Sheets as the action app and authorize.
4. Choose Create Spreadsheet Row.
5. Select the spreadsheet and worksheet, then map Newie fields to each column header.
6. Test, then turn on the Zap.

## Notes

* Don't rename spreadsheet headers once the Zap is live without remapping the Zap fields.
* For high-volume accounts, consider a single "Events" sheet with a Type column rather than one tab per Newie trigger; it's easier to pivot.
* Google Sheets has a spreadsheet cell limit, not a fixed row limit. More columns mean fewer possible rows, and very large sheets can become slow before they hit the limit. For long-lived logs, periodically archive older rows into another file.

*Last updated: 2026-06-26*