How to Send Gumroad Sale Alerts to a Shared Room

To send a Gumroad sale alert to a small group of phones, use Zapier's instant Gumroad Sale trigger, then send fixed copy to a PingRoom incoming webhook. Map only the stable Gumroad sale ID into PingRoom's replay fields. Keep the buyer, product, price, quantity, license, subscription, affiliate, and order details in Gumroad.

The Room receives only Gumroad sale recorded and Open Gumroad to review the sale. Gumroad remains the sales record.

This is a Zapier webhook recipe, not a native Gumroad integration. It requires a Gumroad account, a paid Zapier plan that includes Webhooks by Zapier, and PingRoom Pro for the destination Room's incoming webhook.

Start with Gumroad's own notifications

Gumroad lets sellers configure email or push notifications through its Dashboard app. If one authorized seller needs the normal sale details, use those notifications first.

Add a shared Room only when a small, stable group needs one sparse signal and should open Gumroad under their own access for everything else.

A Ping does not prove that a sale is final, a payment is settled, a refund will not follow, a license was delivered, somebody reviewed the order, or every phone displayed the alert. It says only that the selected Gumroad trigger produced an automation event.

Prepare one private Room

Create or choose a private PingRoom Room for the people who genuinely need the signal. Open Settings → Connections → From another app, add an incoming webhook named Gumroad sale, keep Quick Ping on Custom message, save it, and copy the complete secret URL.

The incoming-webhook guide covers the Room-side setup. The webhook reference carries the current fields, text limits, idempotency behavior, cooldown, and errors.

Treat the full URL as a password. Keep it out of Gumroad fields, browser-side code, screenshots, shared documents, and logs. Regenerate the webhook secret if it is exposed.

Build the sale-to-Room Zap

Zapier currently lists Gumroad's Sale trigger as instant and Custom Request as an available Webhooks by Zapier action. Custom Request lets you provide the exact JSON and headers PingRoom expects.

In a new Zap:

1. Choose Gumroad as the trigger app.
2. Choose Sale.
3. Connect the intended Gumroad seller account.
4. Load a harmless test sale and identify its stable sale ID in the trigger sample.
5. Add Webhooks by Zapier as the action and choose Custom Request.
6. Set the method to POST, paste the PingRoom webhook URL into URL, and set data pass-through to No.
7. Put this exact JSON in the Data field:

{
  "action": null,
  "title": "Gumroad sale recorded",
  "message": "Open Gumroad to review the sale.",
  "correlation_id": "gumroad-sale-{{Gumroad sale ID}}"
}

Use Zapier's field picker to replace {{Gumroad sale ID}} with the sale ID from the trigger sample. Do not type the sample value permanently, and do not map any other trigger field.

Add these headers:

Zapier's webhook action guide warns that an empty Data field can pass every field from the previous step into the request. Fill the body explicitly and inspect the test request before turning the Zap on.

Never map these Gumroad fields into the PingRoom request:

• buyer name, email, user ID, or IP address;
• product name, permalink, variant, custom fields, or quantity;
• price, currency, fees, tax, discount, or affiliate data;
• license key, subscription ID, recurrence, or membership status;
• order number, receipt URL, dispute, refund, or shipping details.

The sale ID is used only as a replay identity. It should not appear in the notification copy, and people should open Gumroad under its own permissions to inspect the record.

These AI-generated editorial illustrations feature approved PingRoom avatars and Pingo the Pigeon, PingRoom's fictional Chief Marketing Officer. They are not Gumroad, Zapier, or PingRoom screenshots and do not depict customers.

Pingo is beside the duplicate gate because he can inspect a repeated signal without opening a sales record. He cannot access Gumroad, read a private Room, run the Zap, or send a Ping. People choose the seller account, Room members, copy, and response process.

Rehearse the privacy and replay boundary

Use a test product or made-up sample data and a Room whose members expect the rehearsal.

1. Trigger one harmless test sale. Confirm the Zap starts with Sale and not Refund, Cancellation, or New Product.
2. Inspect the outgoing request. It should contain only the four JSON fields and two headers above.
3. Confirm one Ping appears with the fixed title and message.
4. Retry the same action with the same sale ID and unchanged body. PingRoom should replay the first accepted result instead of creating another Ping.
5. Change the body but keep the old idempotency key. The request should conflict rather than silently changing the first event's meaning.
6. Trigger a second harmless test sale. Its different sale ID should create one new Ping.
7. Check Zapier's task history and confirm no buyer or order field was sent to PingRoom.
8. Lock a test phone and read the alert as a bystander would. The copy should reveal no commercial detail.

For this article, representative Gumroad-shaped sale IDs passed through the recorded request builder and a local mock of PingRoom's documented contract. The checks covered first acceptance, exact replay, changed-body conflict, a second sale, malformed identity, fixed private copy, excluded commercial fields, and a disabled webhook. They used no live Gumroad account, Zapier account, PingRoom Room, buyer, sale, phone, or delivery receipt.

Do not paste the PingRoom URL into Gumroad Ping

Gumroad's Advanced settings also include Ping, a direct post-sale automation endpoint. That is a different integration path from the Zap above.

Gumroad Ping sends form-encoded sales data to one endpoint. This recipe needs a deliberately small JSON body plus an Idempotency-Key header. Pasting the PingRoom URL directly into Gumroad would give up that copy and privacy boundary.

If you already operate a server-side commerce receiver, you can accept Gumroad Ping there, establish the event's trust under Gumroad's current API guidance, retain a durable sale identity, and then send fixed copy to PingRoom. That developer workflow deserves its own threat model and tests; it is not a one-field replacement for this Zap.

Treat sales state and delivery honestly

Zapier labels Sale as instant, but that does not make the end-to-end path a financial or fulfillment control. Zapier execution, network delivery, PingRoom acceptance, phone connectivity, Focus mode, notification permission, Room settings, and operating-system policy can all affect what one phone displays.

PingRoom's HTTP success means the Ping was accepted into its normal path. It does not prove payment settlement, order review, delivery, accounting entry, refund status, or device display. Gumroad and Zapier remain the places to inspect the sale record and automation run.

Send the smallest useful signal

If each Gumroad sale deserves one shared attention signal, create the private Room and incoming webhook, connect one harmless test sale, and keep every commercial detail in Gumroad.

Gumroad and Zapier are trademarks of their respective owners. PingRoom is not affiliated with or endorsed by them.