Add Paddle customers to Close as leads
A Paddle + Close agent flow
A new customer checks out through Paddle, and your sales team in Close has no idea they exist until someone notices revenue went up. For a self-serve product with a sales-assist motion, those fresh paying customers are exactly who you want a rep reaching out to, and the gap between checkout and CRM is where expansion deals quietly die. This recipe closes it: your agent reads new Paddle customers and creates a lead in Close for each, so every paying account lands in the pipeline a rep works. It calls list_customers, diffs against what's already in Close, and for each new one calls create_lead with the customer's name and email, then create_contact to attach the person. Paddle answers on request, so the agent runs on a cadence, pulls customers created since last time, and adds the new ones.
The flow
list_customersLists customers.
create_leadCreates a new lead (company).
Step by step
- Read new Paddle customers
The agent calls list_customers and pages through, keeping the ones created since its last run using the stored timestamp. Each customer record carries the name, email, and Paddle customer ID.
- Check Close for a match
Before creating anything, the agent searches Close by email with lead_search or search so it doesn't make a duplicate lead for a customer a rep already added by hand.
- Create the lead and contact
For a genuinely new customer it calls create_lead with the company or customer name, then create_contact on that lead with the email so the rep can reach the actual person, not just a company shell.
- Track the high-water mark
Store the newest Paddle customer timestamp processed. Next run the agent asks Paddle only for customers after that mark, so it isn't re-scanning every customer each cycle.
Tell your agent
Every hour, list Paddle customers created since your last run. For each one, search Close by email; if no lead exists, create a lead with the customer's name, then create a contact on that lead with their email and a note that they came from Paddle. Track the newest customer you've added so you only pull customers after it next time.
Setup
This flow needs both servers connected to your agent. Follow each install guide:
Worth knowing
- list_customers returns a name and email per customer, but Paddle creates a customer record at checkout, so a brand-new buyer may have a sparse profile. Don't assume a company name; fall back to the email's domain or the customer name when you build the lead.
- create_lead makes a company-level record in Close; the person lives on a separate contact. Call create_contact after create_lead so the rep has someone to email, otherwise the lead is an empty shell.
- Always search Close by email before creating. Without that check, a customer who updates their email in Paddle, or one a rep already entered, becomes a duplicate lead that someone has to merge later.
Questions
- Does it move the lead through the pipeline?
- No. It only creates the lead and contact. Assigning a status, an owner, or a follow-up task is a separate step; you could set a lead status on create or add a task with create_task so a rep picks it up.
- Will it create duplicates if it runs twice?
- Not if it searches first. The email lookup against Close is the guard: the agent only calls create_lead when no existing lead matches, so re-running is safe.