This tutorial is for anyone selling digital products on Gumroad who wants a sales log they own: a Google Sheet that gains one row per sale, with the product, buyer and price, without anyone copying numbers across. It uses two Make modules and no code. Every step below is taken from Make's own documentation for the Gumroad app and the Google Sheets app, read on October 16, 2026 and linked where each is used.
One honest note before starting: Make's Gumroad documentation page carries Make's own warning that it is AI-generated from Gumroad's documentation and may contain mistakes. The module names and connection steps quoted here are what that page states today; if a screen in Make or Gumroad looks different, the vendor page wins.
What you need
- A Gumroad account with at least one product. Make's documentation says the Gumroad app needs an active Gumroad account and an API key, and the connection is made with OAuth2 credentials created in Gumroad's Advanced Settings.
- A Google account. The Google Sheets app needs nothing more; the connection is made by signing in with Google and granting the permissions it asks for.
- A Make account. The Free plan runs up to 2 active scenarios, and this tutorial uses one.
Step 1: Prepare the sheet
Create a new Google Sheet and put column names in the first row, for example Date, Product, Buyer email, Price and Order ID. The names are yours to choose, but having a header row matters: Make's Add a Row module can treat the header names as the names of the fields you map into, which makes the next steps readable. Leave the rows below empty; the module adds a new row at the bottom of the table, so stray notes under the data would be in its way.
Step 2: Create the Gumroad trigger
In Make, create a new scenario and add the Gumroad module Watch New Sales. The documentation lists it as the trigger that fires whenever a product is purchased, and it carries the instant tag, which means Gumroad pushes each sale to Make rather than Make polling for it. Because it is an instant module, the documentation says to click Create a webhook first, then Create a connection.
The connection needs OAuth2 credentials from Gumroad. Per Make's steps: in your Gumroad account, open Advanced Settings from the account menu, create a new application, give it a name, enter the callback URI https://www.integromat.com/oauth/cb/gumroad, create the application, then copy the Client ID and the Client secret it shows. Back in Make, paste those two values into the connection dialog, optionally name the connection, and save. Make adds that the Gumroad interface may have changed since the steps were written, so check Gumroad's own help if a screen does not match.
Three other Gumroad modules are worth knowing for later: Watch New Cancellations triggers when a subscriber cancels, List Sales returns a detailed list of past sales, and Get a Sale retrieves one transaction by its identifier.
Step 3: Add the Google Sheets action
Add a second module after the trigger: Google Sheets, Add a Row. Click Create a connection, then Sign in with Google and grant the requested permissions; the documentation says that is all a standard connection needs. The advanced option of using your own Google Cloud project credentials exists, but it is not required, and Make notes that a project left in Testing status forces the connection to be re-authorised every week.
Then fill the module's fields as Make's module reference describes them:
- Search Method: choose how to pick the spreadsheet. Search by path lets you browse your Drive; Select from all and Enter manually are the alternatives. With Enter manually you paste the Spreadsheet ID, which is the long string in the sheet's URL between /d/ and /edit.
- Sheet Name: the tab inside the spreadsheet that should receive the rows.
- Table contains headers: Yes. With Yes, the module does not treat your header row as data, and the fields you map into are named after your headers rather than A, B, C.
- Use column headers as IDs of the columns: Yes. The documentation explains that header names then act as stable identifiers, so existing mappings keep working if columns are added, removed or reordered, as long as the headers themselves are not renamed.
- Values in columns: map the trigger's output into each column, for example the sale's product name, the buyer's email and the price into the matching headers.
- Value input option: User entered means values are parsed as if typed into the sheet, so numbers stay numbers and date-like text may become dates; Raw stores exactly what was sent. For a ledger, User entered is the usual choice.
- Insert data option: Insert rows, so each sale creates a new row rather than overwriting cells in the range.
Step 4: Test and switch on
Save the scenario and run it once from the editor while making a test purchase of one of your own products; the trigger receives the sale and the sheet gains a row. If the row lands but the columns are shifted, the header settings in the Add a Row module are the first thing to check: with Table contains headers set to No, the module names columns A, B, C and maps by position instead of by name. When the test row looks right, switch the scenario on. Instant triggers need no schedule; they wait for Gumroad to send the next sale.
What it costs in credits
Make bills by credits, and for ordinary apps 1 operation equals 1 credit. Make's operations page explains the rule that matters here: a trigger counts one operation per check, and every later module runs once per bundle the trigger returns. A single sale is one bundle, so each sale costs the trigger's operation plus one Add a Row operation. The Free plan includes up to 1,000 credits a month and 2 active scenarios, which covers a small store comfortably; the paid Core plan, at $9 a month billed annually, moves the allowance to 10,000 credits, with the figures and the monthly-billing prices set out in the Make review on this site.
Two things do not cost anything: the Router module and the error-handler modules, so splitting the scenario later, for instance to also post the sale to a chat channel, does not add a credit for the split itself.
Where to take it next
- Backfill history: a one-off scenario with List Sales feeding Add a Row loads past sales into the same sheet, one row per returned sale.
- Track churn: a second scenario starting from Watch New Cancellations and writing to a second sheet gives a cancellation log for memberships.
- Keep the sheet clean: Update a Row exists for changing a row that already has data, and Make's documentation points to it rather than Add a Row for that case.
Verdict
A Gumroad sales ledger in Google Sheets is a two-module Make scenario: Watch New Sales into Add a Row, connected once with Gumroad's OAuth2 credentials and a Google sign-in. Each sale costs two credits, so the Free plan's 1,000 credits a month cover a small store, and the Core plan's 10,000 credits cover a busy one. The only part that needs care is the header settings in the Sheets module, which decide whether columns are mapped by name or by position.