PayPal logo
Gmail logo

Workflow template

Email completed PayPal payments with Gmail

Email completed PayPal captures with Gmail. Send the capture ID, gross amount, original currency, capture creation time and event ID to a fixed recipient.

How it works

From a completed PayPal capture to an email notification

1 Trigger · 1 Action
PayPal1 · Trigger

Payment · Capture · Completed

Receive verified PAYMENT.CAPTURE.COMPLETED webhooks for the connected PayPal REST app. An approved order, pending capture or authorization alone does not start this workflow.

Gmail2 · Action

Email the completed PayPal capture

Send a plain-text message to your fixed recipient with the capture ID, completed status, gross decimal amount, original currency, capture creation time and webhook event ID.

The result

A concise capture notification in your chosen inbox

Example completed-capture notification

PayPal capture completed: FICTIONAL-CAPTURE-42

PayPal reported a completed capture. Capture ID: FICTIONAL-CAPTURE-42 Status: COMPLETED Gross amount: 49.90 EUR Capture created (UTC): 2026-09-19T09:00:00Z Webhook event ID: WH-FICTIONAL-CAPTURE-42 Payer details and purchase contents remain in PayPal. This is a capture-event notification, not a receipt or settlement confirmation.

Fictional example. The amount is the gross decimal value in its original currency. The timestamp is capture creation time; neither field is a settlement or balance report.

Before activation

Set up your workflow

  1. Connect the PayPal REST app

    Choose the account for the app whose completed captures you want to observe. Use a PayPal Sandbox app and a fictional sandbox payment for the first test.

  2. Choose Gmail and a fixed recipient

    Connect your sending Gmail account and enter an authorized recipient in To. Start with your own inbox. The recipient receives capture metadata; payer details and purchase contents are excluded.

  3. Complete a sandbox capture after connection

    Activate and wait for the PayPal trigger connection to be ready. Complete a new sandbox payment, then compare its capture ID, original amount and currency, creation time and webhook event ID with the email.

Details and limitations
  • Completed captures, not order approvals. Only PAYMENT.CAPTURE.COMPLETED starts the workflow. Approved orders, pending captures, authorizations and legacy sale events do not. Several captures for one order can produce several messages.

  • The amount keeps PayPal’s source meaning. The workflow sends the gross decimal string in the original currency, without dividing by 100, converting currencies or calculating fees. Capture creation time is not settlement time.

  • Only the listed metadata leaves PayPal. Payer names, email addresses, postal addresses, payment instruments, purchase descriptions, attachments and notes are not mapped. Gmail keeps the sent notification in Sent, and the fixed recipient can read the included metadata.

  • This is a one-way notification. Existing payments are not imported. Refunds, reversals, disputes and later changes do not update the email. Manual reruns or ambiguous send failures can send another message; Gmail sending limits apply.

Questions about this template

Will approving a PayPal order send the email?

Not by itself. The trigger listens for PAYMENT.CAPTURE.COMPLETED. Complete a capture after approval; pending captures, authorizations and legacy sales are different events.

Does the email include fees, a converted amount or settlement time?

No. It preserves the gross decimal amount and its original currency. The timestamp is the capture resource’s create_time, not settlement time or webhook arrival time.

Are payer and purchase details copied into Gmail?

No. The mapping includes capture ID, completed status, gross amount, currency, capture creation time and webhook event ID. Payer information, instruments, purchase descriptions, files and notes stay in PayPal.

Can the same payment produce another email?

An order with multiple captures can produce several messages. Manual reruns or ambiguous send failures can also send again. Refunds, reversals, disputes and later changes do not update previous emails.

Explore connected apps