Skip to content
For LLMsView as Markdown·

Paddle ​

undefined

DetailValue
CategoryFinance
Base URLhttps://api.paddle.com
AuthenticationBearer Token
Endpoints5
Connector keypaddle

Using Paddle in a workflow ​

  1. Go to Connections and click New Connection.
  2. Pick Paddle 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 Prices
GET Subscriptions
GET Transactions
GET Customers

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 Paddle 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 Paddle API reference.

GET ​

Prices

DetailValue
Operation IDprices_1
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Paddle connection from the Connection dropdown.
  3. In the Operation dropdown, select prices_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 Paddle API reference.

GET ​

Subscriptions

DetailValue
Operation IDsubscriptions_2
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Paddle connection from the Connection dropdown.
  3. In the Operation dropdown, select subscriptions_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 Paddle API reference.

GET ​

Transactions

DetailValue
Operation IDtransactions_3
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Paddle connection from the Connection dropdown.
  3. In the Operation dropdown, select transactions_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 Paddle API reference.

GET ​

Customers

DetailValue
Operation IDcustomers_4
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Paddle connection from the Connection dropdown.
  3. In the Operation dropdown, select customers_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 Paddle API reference.