# Paddle integrations: products and prices

> Create a product, create a price and create a customer in Paddle, and start a workflow when Paddle sends “Transaction completed”.

**Canonical page:** https://tray.ai/connectors/paddle-integrations/
**Categories:** Finance
**Connects through:** HTTP Connector

## Overview

Paddle is a merchant of record billing platform for software companies, handling checkout, subscriptions, invoices, sales tax, and payouts. Tray.ai connects to Paddle through the HTTP Connector, so your workflows can call the Paddle API alongside the rest of your stack.

## Use cases

### Products

Read, create, and update products in Paddle from any Tray.ai workflow. The Paddle API covers calls such as list products and create a product.

- List products
- Create a product
- Update a product

### Prices

Read, create, and update prices in Paddle from any Tray.ai workflow. The Paddle API covers calls such as list prices and create a price.

- List prices
- Create a price
- Update a price

### Customers

Read, create, and update customers in Paddle from any Tray.ai workflow. The Paddle API covers calls such as list customers and create a customer.

- List customers
- Create a customer
- Update a customer

### Subscriptions

Read and update subscriptions in Paddle from any Tray.ai workflow. The Paddle API covers calls such as list subscriptions and get a subscription.

- List subscriptions
- Get a subscription
- Update a subscription

### Transactions

Read, create, and update transactions in Paddle from any Tray.ai workflow. The Paddle API covers calls such as list transactions and create a transaction.

- List transactions
- Create a transaction
- Update a transaction

### Adjustments

Read and create adjustments in Paddle from any Tray.ai workflow. The Paddle API covers calls such as list adjustments and create an adjustment.

- List adjustments
- Create an adjustment

## Challenges Tray.ai solves

### Keeping Paddle credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Paddle credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Paddle API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Paddle API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Paddle?

Yes. Tray.ai connects to Paddle through the HTTP Connector, which calls the Paddle API directly. Any call the Paddle API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Paddle?

The Paddle API uses a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Paddle connector?

Paddle runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Paddle connector from the Paddle API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/