Paddle

undefined

Detail	Value
Category	Finance
Base URL	https://api.paddle.com
Authentication	Bearer Token
Endpoints	5
Connector key	paddle

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

Endpoint	Summary
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

Detail	Value
Operation ID	products_0
Method	GET
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

Detail	Value
Operation ID	prices_1
Method	GET
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

Detail	Value
Operation ID	subscriptions_2
Method	GET
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

Detail	Value
Operation ID	transactions_3
Method	GET
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

Detail	Value
Operation ID	customers_4
Method	GET
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.