Skip to content
For LLMsView as Markdown·

Gumroad

undefined

DetailValue
CategoryFinance
Base URLhttps://api.gumroad.com/v2
AuthenticationOAuth2
Endpoints5
Connector keygumroad

Using Gumroad in a workflow

  1. Go to Connections and click New Connection.
  2. Pick Gumroad from the marketplace.
  3. Enter your credentials (see Authentication above for what's expected).
  4. In a workflow, drop an API Call node and select this connection.
  5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

EndpointSummary
GET Products
GET Sales
GET Subscribers
GET Offer Codes
GET User

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET

Products

DetailValue
Operation IDproducts_0
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Gumroad connection from the Connection dropdown.
  3. In the Operation dropdown, select products_0.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Gumroad API reference.

GET

Sales

DetailValue
Operation IDsales_1
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Gumroad connection from the Connection dropdown.
  3. In the Operation dropdown, select sales_1.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Gumroad API reference.

GET

Subscribers

DetailValue
Operation IDsubscribers_2
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Gumroad connection from the Connection dropdown.
  3. In the Operation dropdown, select subscribers_2.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Gumroad API reference.

GET

Offer Codes

DetailValue
Operation IDoffer_codes_3
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Gumroad connection from the Connection dropdown.
  3. In the Operation dropdown, select offer_codes_3.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Gumroad API reference.

GET

User

DetailValue
Operation IDuser_4
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

  1. Add an API Call node to your workflow.
  2. Pick your Gumroad connection from the Connection dropdown.
  3. In the Operation dropdown, select user_4.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Gumroad API reference.