When a Paddle transaction completes
Reads the completed Paddle transaction with its amount, currency, and customer so the payment lands as a Well transaction.
Trigger·Transaction
Integrations · Payments and bankingConnect Paddle to Well
Sync Paddle invoices, transactions, and customer records into your workspace via the Well-hosted Paddle MCP server
What Well pulls from Paddle
Paddle feeds invoice, transaction, company record into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Paddle’s access.
| From Paddle | In Well | Relation | |
|---|---|---|---|
| Invoice | Receivable | Becomes | |
| Transaction | Ledger line | Becomes | |
| Company record | Customer | Enriches | |
| Person record | Contact | Resolves to |
- Sync mode
- incremental polling
- Refresh
- scheduled
- Direction
- Paddle → Well
4 triggers from Paddle.
When a Paddle transaction invoice is available
Pulls the invoice generated for a transaction with its line items and totals so the receivable can be reconciled.
Trigger·InvoiceWhen a Paddle subscription renews
Detects the renewal charge for a subscription with its plan and period for clean recurring-revenue tracking.
Trigger·TransactionWhen a Paddle adjustment or credit note is issued
Captures a refund or credit note with its amount and originating transaction so adjustments stay matched.
Trigger·Invoice
What Well does with your Paddle connection
Connect
Connect Paddle over OAuth 2.0: you approve on Paddle's authorize screen, so the password never reaches Well; Well holds only a scoped token it can refresh.
Sync
Well brings invoice, transaction, and company record in from Paddle on a recurring poll that fetches only what changed since the last read. The first sync backfills history in the background and the connection stays live after.
Enrich
Well resolves each Paddle entity into receivable, ledger line, and customer, assigns categories, and links every record to an audit trail across the rest of your connected tools.
Available
Your data from Paddle lands in the workspace as receivable, ledger line, and customer you can search, chart, and automate.
Questions Paddle unlocks
Ask in plain language. Well answers from your connected Paddle connection, resolved against the rest of your stack.
Ask Well
Ask anything about your Paddle connection
Summarise this month
What needs attention?
Find unmatched records
Ask about your Paddle connection…
1 agent skill runs on Paddle.
Well lists Paddle in the connection check every skill runs before it answers. No skill reads it for a figure yet.
Connects and checks Paddle
Connect Paddle in three steps
- 01
Connect your Paddle account
Authorize Well to access your Paddle account through the connection portal.
- AuthOAuth 2.0
- Accessread-only
- 02
Map your entities
Confirm the connection to allow the Well-hosted Paddle MCP server to read your invoices, transactions, and customer records.
- Mappingpreconfigured by Well
- 03
Use the data
Verify that your Paddle data is visible in your workspace and ready for reconciliation.
- First syncstarts as soon as connect completes
This connection is read-only and will not alter any data inside your Paddle account.
How Paddle stays secure with Well
Well calls Paddle's API with an OAuth 2.0 token scoped to invoice, transaction, company record, and person record. Paddle's consent screen shows you the same list before you approve. Paddle enforces scope server-side; authentication runs entirely through Paddle's authorize screen so Well never sees your credentials. Tokens refresh automatically; rotation is one click away.
OAuth 2.0Encrypted at restGDPR compliant
Read the full privacy and security policyScopes Well requests
- granted
Read Paddle records
Endpoints the Paddle API token grants, scoped by your consent.
- granted
Resolve invoice, transaction, company record, and person record across your stack
Match identifiers in Paddle against the same entities your other connected tools expose, so each record carries cross-tool context.
- refused
Modify or delete Paddle records
Not granted; Paddle is read-only in Well. Write-back is opt-in per connector when a write surface exists.
- refused
Store Paddle passwords or session cookies
Authentication runs through OAuth 2.0 tokens we never see.
Disconnect any time from Well settings or Paddle’s admin panel.
Frequently asked questions about Paddle and Well
How does Well retrieve data from my Paddle account?
Well uses a hosted Model Context Protocol server to pull your Paddle invoices, transactions, companies, and people records directly into your workspace.
Can Well update or modify my invoices directly inside Paddle?
No. Well only reads your data to help you match and reconcile records. It does not write, edit, or push any transactions or customer details back to Paddle.
How often does Well retrieve my Paddle transaction records?
Well syncs your Paddle data in the background, ensuring your workspace has access to the latest invoices and customer details without manual exports.
Pairs well with Paddle
More in Payments and banking
Popular cross-category
Ready to connect Paddle?
Connect once. Every invoice, transaction, company record from Paddle becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.