Weekly Paddle sales recap in Slack
Every Monday, Letaido posts last week's Paddle revenue, new subscriptions and cancellations to Slack, with the change from the week before.
Letaido's Paddle integrations give an AI agent your Paddle Billing sales, subscriptions and catalog, and let it act on them in 64 other apps.
Revenue, onboarding and win-back jobs. Open one to watch it run.
Every Monday, Letaido posts last week's Paddle revenue, new subscriptions and cancellations to Slack, with the change from the week before.
Every morning, Letaido marks yesterday's new Paddle subscribers as customers in HubSpot, with the plan they bought.
Every morning, Letaido drafts a short personal welcome in Gmail to each new Paddle subscriber, naming the plan they chose.
Every Monday, Letaido adds last week's Paddle revenue for each product to your revenue sheet, with the change from the week before.
Every day, Letaido tags customers who cancelled in Paddle so your Kit win-back sequence reaches them.
Describe a plan and Letaido creates the Paddle product with its monthly and yearly prices, after checking the name is new.
Five ways to use Paddle data in other apps.
| Option | Set up by asking | Reads sales and subscriptions | Runs unattended | No code | Connects thousands of apps |
|---|---|---|---|---|---|
| Yes | Yes | Yes | Yes | No | |
| Paddle's own integrations | No | Partly | Yes | Yes | No |
| Make and similar | No | Partly | Yes | Yes | Yes |
| Paddle API and webhooks | No | Yes | Yes | No | Partly |
| Paddle MCP server | Yes | Yes | No | Yes | No |
| Option | How it works | Best for | Watch out for |
|---|---|---|---|
| Letaido AI agent | You describe the job. The agent reads Paddle's sales, subscriptions and events, decides what matters and acts in 64 other apps. | Recaps, welcome notes and win-back lists that need a judgement call. | 65 apps, not thousands. Jobs run on a schedule or when you ask, not on Paddle webhooks. |
| Paddle's own integrations | Integrations Paddle lists on its site, such as HubSpot and Intercom, that sync subscription data. | Billing fields on CRM records for segments and workflows. | A short list of tools, and it syncs data rather than acting on it. |
| Make and similar | Workflow modules that create customers, prices, products and transactions, and get customers, prices and products. | Moving one record type, such as a new customer, into another tool. | Every scenario is built and repaired by hand, module by module. |
| Paddle API and webhooks | Developers call the API with a scoped API key and receive webhooks at notification destinations they set up. | Checkout, provisioning and billing screens inside your product. | You need engineers to write and maintain the code. |
| Paddle MCP server | An MCP server from Paddle that lets AI coding tools read and change your Paddle account. | Pricing changes, billing questions and reports while you chat. | Only works inside a chat, with no schedule of its own. |
Connect Paddle once. After that, you describe each job in plain English.
Allow all read operations once per app; approve each kind of write once.
A schedule starts the job, or you do by asking.
In Paddle, open Developer Tools, then Authentication, and create an API key with the permissions your jobs need, such as reading transactions, subscriptions, customers and events.
Letaido tells from the key whether it's a sandbox or a live key, so there is nothing else to choose.
Sandbox and live are separate Paddle accounts with their own keys. Switch to a live key once the test runs look right.
Ask for the job in a chat, read the output, and when it looks right, tell Leta how often to run it.
18 actions across products, prices, customers, subscriptions, transactions and events.
Create an API key under Developer Tools, Authentication in Paddle, with the permissions your jobs need, and paste it into Letaido. Sandbox and live keys both work; use one per environment.
No. Letaido's connector works with Paddle Billing and its current pdl_ API keys.
No. Paddle jobs run on a schedule and read Paddle's event list for the last day or week, like the daily win-back tags, or they run when you ask.
Yes. Paddle offers an MCP server that AI coding tools use to read and change your account while you chat. Letaido is not an MCP server. It has its own Paddle connector, mixes Paddle with your other apps and runs jobs on a schedule.
Paddle lists a HubSpot integration that syncs subscription data. With Letaido, the agent can also mark each new Paddle subscriber as a customer in HubSpot every morning, as in the job above.
Yes. Paste a sandbox key, run the job on test data, then add a live key when it looks right. Sandbox and live are separate Paddle accounts.
Allow all read operations once per app; approve each kind of write once.
Connect Paddle, then ask for a job like "Post a weekly Paddle sales recap in Slack". Leta gets it done on your schedule, or the moment you ask.
Get LetaidoCreate, update, and list products in your Paddle catalog.
Create, update, and list prices attached to your Paddle products.
Create new customers, look up a single customer, or list all customers in your Paddle account.
Generate a customer portal session so buyers can self-manage their account.
Fetch a single subscription or list all subscriptions to see their current status and details.
Cancel an active subscription, ending future billing for the customer.
Create server-controlled transactions and fetch or list transactions to confirm payment status.
List account events in chronological order to audit activity or trigger downstream workflows.
Mint a client-side token for Paddle.js to enable checkout on your front end.