Gumroad & Payhip Sales Webhook to Google Sheets (n8n)

One sales ledger for Gumroad + Payhip—automatically sync into Google Sheets via n8n webhooks

This n8n workflow listens to Gumroad and Payhip sales events and writes a unified, de-duplicated sales log into Google Sheets—so you don’t need separate CSV exports or manual reconciliation.

What this workflow does

• Receives events from two webhooks: one for Gumroad (Ping) and one for Payhip (paid/refunded).
• Verifies each request: Gumroad requests are validated using your seller_id, and Payhip requests are verified using the signature (SHA-256 of your API key). Anything else is ignored.
• Normalizes both platforms into one schema with fields like order ID, platform, status, date, product, quantity, currency, gross, fees, net, and buyer email.
• Appends or updates rows by order ID: webhook retries won’t duplicate entries, and refunds update the original sale. Payhip fees are included so net is calculated correctly.

How to set it up

• Create a Google Sheet with a Sales tab and the header row specified in the workflow’s main sticky note.
• Add your Gumroad seller ID and the SHA-256 hash of your Payhip API key into the two check nodes.
• Connect Google Sheets, paste your sheet URL, publish, then paste the production webhook URLs into:
  • Gumroad: Settings > Advanced > Ping
  • Payhip: Settings > Developer > Webhooks

Use cases

• Run one combined sales ledger for digital products sold on both Gumroad and Payhip.
• Keep refunds and retries accurate without manual edits.
• Give operators and SaaS dashboards a single source of truth in Google Sheets.

Technical details

• n8n nodes/workflow components: webhook, if, code, sticky note, Google Sheets.
• Customization: add columns in the two Normalise code nodes.