tr Skip to content
Black Friday FlowMattic for life, 12 payments of $33.25 Or $399 once. Nothing added for splitting Ends in --Days --Hrs --Min --Sec See the deal

Connect Chip and Google Sheets

Chip reports each purchase from creation to payment, plus refunds, holds and payouts to your bank. FlowMattic writes those events to Google Sheets, giving a merchant a sales ledger that updates itself, a list of payments that failed and a payout record to match against bank statements, all in a spreadsheet the bookkeeper already uses.

27 triggers 19 actions 6 example workflows 2 ready-made templates Unlimited runs

Try a pairing

When this happens in Chip21 triggers

Do this in Google Sheets19 actions

1. TriggerPurchase Paid
2. ActionAdd New Row

When Chip fires Purchase Paid, 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

Chip 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.

Chip app icon Google Sheets app icon Ready-made template

Log every paid Chip purchase in a sheet

Each paid purchase adds a row with the purchase ID, client, product, amount and date, a running sales ledger outside the Chip dashboard.

Purchase PaidAdd New Row

View the template
Chip app icon Google Sheets app icon

Open a row at checkout and close it on payment

Purchase Created adds a pending row. When the purchase is paid, the lookup finds that row and the Router updates it, adding a fresh row only if the creation event was missed.

Purchase PaidLookup Row DataRouterUpdate RowAdd New Row

Chip app icon Google Sheets app icon

Mark sales as refunded in the ledger

Payment Refunded finds the purchase by ID and writes the refund amount and date into its row, so net sales in the sheet match what you actually kept.

Payment RefundedLookup Row DataUpdate Row

Chip app icon Google Sheets app icon

Collect failed payments for a follow-up call

Purchase Payment Failure adds the client and amount to a follow-up tab, so someone can contact buyers whose card or bank payment did not go through.

Purchase Payment FailureAdd New Row

Chip app icon Google Sheets app icon

Record payouts and email finance when one fails

Successful payouts go to a payouts tab for bank matching. A separate workflow on Payout Failed logs the failure and emails finance so the bank details get checked.

Payout FailedAdd New RowEmail (SMTP)

Chip app icon Google Sheets app icon

Track preauthorised holds waiting to be captured

Merchants who hold funds before shipping log each preauthorisation, then mark the row when Purchase Captured or Purchase Released arrives, so no hold is forgotten.

Purchase PreauthorizedAdd New Row

Set up: paid purchases in a ledger

At the end, each purchase paid through Chip adds a row to your sales ledger in Google Sheets.

  1. Prepare the ledger

    Create a sheet with Purchase ID, Date, Client name, Email, Product, Amount and Currency columns.

  2. Trigger on Purchase Paid

    Create a workflow with Chip and Purchase Paid, and set up the connection the trigger asks for in your Chip account.

  3. Pay a test purchase

    Complete one purchase so FlowMattic captures the paid purchase and its fields.

  4. Write the ledger row

    Connect Google Sheets, add Add New Row, map the purchase fields to the columns, test the step and switch the workflow on.

Import the ready-made template Beginner, about 5 min to set up
Log every paid Chip purchase in a sheet Template
  1. Chip app icon 1. Trigger in Chip Purchase Paid
  2. Google Sheets app icon 2. Action in Google Sheets Add New Row

    Fields mapped from the earlier steps (a typical setup)

    From ChipTo Google Sheets
    Purchase IDPurchase ID
    Client full nameClient name
    Client emailEmail
    Product nameProduct
    TotalAmount
    CurrencyCurrency
    Paid onDate
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

  • Amount fields may arrive in the smallest currency unit, such as sen rather than ringgit. Check your test data and divide with Number Formatter if needed.
  • Refund, capture and release workflows find rows by purchase ID, so keep that ID in its own column.
  • Purchases have many pending states with their own triggers. Pick the ones your business uses rather than logging all of them to one tab.

Triggers (21)

  • Purchase CreatedTriggers when a new purchase is created.
  • Purchase PaidTriggers when a purchase is paid
  • Purchase HoldTriggers when a purchase is on hold.
  • Purchase CancelledTriggers when a purchase is canceled.
  • Purchase CapturedTriggers when a purchase is canceled.
  • Purchase PreauthorizedTriggers when a purchase is preauthorized.
  • Purchase ReleasedTriggers when a purchase is released.
  • Purchase Recurring Token DeletedTriggers when a recurring token of purchase is deleted.
  • Purchase Payment FailureTriggers when a payment of purchase is failed.
  • Payout SuccessTriggers when there is payout success.
  • Payout FailedTriggers when there is a payout failed.
  • Payout PendingTriggers when there is a pending payout.
  • Payment RefundedTriggers when a payment is refunded.
  • Purchase Pending CaptureTriggers when a pending purchase is captured.
  • Purchase Pending ChargeTriggers when a charge is pending of the purchase.
  • Purchase Pending ExecuteTriggers when a pending purchase is executed.
  • Purchase Pending Recurring Token DeleteTriggers when a recurring token is deleted for pending purchase.
  • Purchase Pending RefundTriggers when a pending refund is for purchase.
  • Purchase Pending ReleaseTriggers when a pending purchase is released.
  • Purchase Subscription Charge FailureTriggers when a subscription charge of purchase is failed.
  • Billing Template Client Subscription Billing CancelledTriggers when billing template client subscription billing cancelled.
Google Sheets app icon

Google Sheets

Integration page

Triggers (6)

  • 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

Chip and Google Sheets connect through FlowMattic on your own site, with no separate automation account in the middle and no charge per run.

Sales and payouts in one file

Paid purchases, refunds and payouts sit on tabs of one spreadsheet, which makes matching Chip to your bank statement a sheet job.

Client data stays on your server

Names, emails and amounts pass from Chip through your own WordPress site to Google, not through an outside automation account.

Every sale logged at one price

Runs are unlimited, so a busy sales month costs no more in FlowMattic than a slow one.

Common questions

Which Chip events can I log in Google Sheets?

Any Chip trigger listed below, including Purchase Created, Purchase Paid, Payment Refunded, Purchase Payment Failure and the payout events. Each one starts its own workflow and can write to its own tab.

Can a refund update the original sale row?

Yes. Start from Payment Refunded, search the purchase ID column with Lookup Row Data and write the refund details with Update Row.

Why do amounts look a hundred times too large?

Payment platforms often send amounts in the smallest unit of the currency. Divide by one hundred with Number Formatter before Add New Row, or format the column in Google Sheets.

Can I match payouts to bank deposits?

Yes. Log Payout Success on its own tab with the amount and date. Each row then lines up with a deposit on your bank statement.

Did not find your answer? You can browse the help center or ask us directly.

Start automating Chip and Google Sheets

Install 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 27 Oct 2026. The example workflows are written with AI from the real triggers and actions of both integrations and checked against them. Chip integration 1.0.0, Google Sheets integration 2.2.4.