PayPal logo
Google Sheets logo

Workflow template

Log completed PayPal payments in Google Sheets

Log completed PayPal capture events in Google Sheets. Record capture ID, status, gross amount, original currency, capture creation time and webhook event ID as six RAW values.

How it works

From a completed PayPal capture to an event-register row

1 Trigger · 1 Action
PayPal1 · Trigger

Payment · Capture · Completed

Receive PAYMENT.CAPTURE.COMPLETED events for the connected PayPal REST app. Approved orders, pending payments, authorizations and legacy sale events are not this trigger’s source.

Google Sheets2 · Action

Append completed capture to the register

Append capture ID, status, gross decimal amount, currency, capture create_time and webhook event ID into A–F. Preserve the source amount without division or currency conversion, using RAW and INSERT_ROWS.

The result

A capture-event record with its original amount and currency

Optional A–F headers in the prepared mapping order.
Capture IDStatusGross amountCurrencyCapture created UTCWebhook event ID
FICTIONAL-CAPTURE-42COMPLETED49.90EUR2026-09-19T09:00:00ZWH-FICTIONAL-CAPTURE-42

Fictional capture. 49.90 is the source gross decimal amount, not cents or a converted value. Capture creation time is not settlement time or webhook-arrival time. This is an event register, not a balance, tax or accounting ledger.

Before activation

Set up your workflow

  1. Connect a PayPal sandbox REST app for testing

    Select the PayPal connection for the app whose completed captures you want to observe. Use a sandbox app and a fictional completed sandbox payment for the first test; an approved order alone is not a completed capture.

  2. Choose the six-column Sheets register

    Connect Google Sheets and use Browse to select a spreadsheet and worksheet. An empty worksheet works without headers; optionally add the displayed A–F labels yourself. Retain RAW and INSERT_ROWS.

  3. Wait for Connected before the sandbox capture

    Activate and wait for the trigger to show Connected, then complete a fictional sandbox capture. Compare the capture and event IDs, gross amount, original currency and capture creation timestamp in the row.

Details and limitations
  • Each capture has its own row. An order with several captures can produce several rows. The trigger is specifically PAYMENT.CAPTURE.COMPLETED; it does not log an order merely being approved, a pending payment or an authorization.

  • Amounts and timestamps retain source meaning. The gross amount is a decimal string in the original currency. No division by 100 or conversion occurs. The mapped time is capture creation time, not settlement time or the time the webhook arrived.

  • Later financial events do not update this history. Existing payments are not imported. Refunds, reversals, disputes and later changes do not update previous rows, and manual reruns can duplicate a row. The register does not represent a current balance or accounting ledger.

  • Only capture and event metadata are copied. Payer names, email addresses, addresses, payment instruments, item details and notes are excluded. RAW prevents formula-looking strings from being evaluated. The append action uses an existing worksheet and does not create headers.

Questions about this template

Will an approved order or pending payment create a row?

Not through this trigger. It listens for PAYMENT.CAPTURE.COMPLETED, not order approval, pending payments, authorizations or legacy sale events. One order can have several completed captures and rows.

Should I divide Gross amount by 100?

No. The workflow preserves PayPal’s gross decimal string in its original currency, such as 49.90 EUR. It performs no cents conversion, currency conversion or fee calculation.

Does Capture created UTC show settlement or webhook arrival?

No. It is the capture resource’s create_time. Settlement time and webhook-arrival time are not mapped into the row.

Will refunds or disputes keep this sheet up to date?

No. Later refunds, reversals, disputes and changes do not update prior rows, and old payments are not imported. Treat this as a capture-event register; manual reruns can duplicate rows.