[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Convert qualified Copper leads to people and deals

> Convert qualified Copper leads to a person and an opportunity by your own rule, skip duplicates and keep unclear ones for yourself. Runs daily.

Source: https://cotlet.dev/integrations/copper-crm-api-mcp-server/convert-qualified-leads

New leads pile up in Copper with the status Open, and every few days someone decides which ones are real and walks each through the Convert Lead dialog by hand.

Cotlet does it in your own Copper CRM account with list\_leads, list\_people and convert\_lead, called by your AI agent, an n8n workflow or a script.

[Sign up free](https://cotlet.dev/app/signup?app=copper-crm) [All Copper CRM tools](https://cotlet.dev/integrations/copper-crm-api-mcp-server.md)

Hosted · nothing to install or maintain

## Can Copper CRM do this on its own?

Copper converts a lead only from the Convert Lead dialog or through the Developer API (checked 20 Oct 2026). The Zapier app has triggers and actions for leads but none to convert one, and Workflow Automation's help article lists no conversion. The API route needs your own code and key.

## How you do it in Copper CRM today

1. Leads are a Professional and Business feature and off by default. An admin switches them on under Workspace Settings > Customize > Lead Statuses > Enable Leads.
2. Open the Leads section, filter by Lead Status and open each lead, full screen or in the side panel.
3. Fill in the Details section, then click Convert Lead in the Details tab.
4. In the dialog, set the owner and the Contact Type, and tick the option to create an opportunity at the same time.
5. For the opportunity, enter the Pipeline Record Name, the Pipeline, a close date and a value, then click Convert and confirm.

## How to convert qualified Copper leads to people and deals

Prompt

```
Go through Open leads in Copper. Convert the ones with a company and a work email to a person with a deal in the Sales pipeline, and leave the rest for me with a one-line reason.
```

1. 01  
### List the open leads  
list\_leads returns leads with the status you name, here Open, with their company and email. The agent follows next\_cursor until it comes back empty. If Leads are switched off in your workspace, the call fails and says so, and the run stops.
2. 02  
### Apply your rule  
Each lead is matched against the rule in your prompt, for example "has a company and a work email". Free-mail addresses and leads without a company go to your list, each with the reason.
3. 03  
### Look for the person first  
list\_people searches the email of every qualifying lead. A lead whose person already exists is not converted, because Copper would create a second person, and the agent lists it for you to merge by hand.
4. 04  
### Convert with a deal  
convert\_lead creates the person, the opportunity in the pipeline you named, and removes the lead. It fails when a required field of the person or the opportunity is empty, and the error names the field, so that lead goes on your list. Each call waits for your OK by default, because a person cannot be turned back into a lead.
5. 05  
### Report the batch  
The agent returns the people and deals it created, and the leads it left, with the reason for each.

### What you get back

Example data

```
Open leads: 12
Converted 7 to a person with a Sales deal (e.g. Dana Whitfield, Brightside Clinic rollout, 12000)
Left for you 5:
- Lee Park: personal email, no company
- Marta Cole: person already exists (marta@brightside.example)
Failed 0
```

### Other ways to ask

- Every morning, convert Open leads from the webinar source and set Contact Type to Potential Customer.
- Convert only leads that mention a budget in the description, with no opportunity, and tell me the count.
- Show me the Open leads that would convert under my rule, but convert nothing.

## What Copper CRM allows, and what to know first

- Leads are a Professional and Business feature in Copper and are off until an admin turns them on under Customize > Lead Statuses.
- The default Lead Statuses are New, Open, Unqualified and Junk, and a workspace can add its own.
- Copper does not convert a lead to a person while required fields of the person are empty, and a required field of the opportunity blocks conversion with a deal.
- Copper cannot turn a person back into a lead.
- The Developer API removes the lead after converting it, and creates a company only when you give it a new name.

convert\_lead asks for your OK by default. To run it daily without you, switch confirmation off for that tool in your dashboard.

Sources: [Copper Help: Working with Leads](https://support.copper.com/en/articles/8823251-working-with-leads) · [Copper Help: Working with People](https://support.copper.com/hc/en-us/articles/115003765692-Working-with-People) · [Copper Developer API: Convert a Lead](https://developer.copper.com/leads/convert-a-lead.html) · [Copper triggers and actions on Zapier](https://zapier.com/apps/copper/integrations)

## Call convert\_lead from a script

curl

```
curl -X POST https://cotlet.dev/api/v1/copper-crm/leads/52710344/convert \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"contact_type":"Potential Customer","opportunity_name":"Brightside Clinic rollout","pipeline":"Sales","close_date":"2026-12-15","monetary_value":12000}'
```

Example response

```
{
"person": {
"person_id": "77121902",
"name": "Dana Whitfield",
"contact_type": "Potential Customer"
},
"opportunity": {
"opportunity_id": "31850018",
"name": "Brightside Clinic rollout",
"pipeline": "Sales",
"stage": "Discovery",
"monetary_value": 12000,
"close_date": "2026-12-15"
},
"lead_removed": true
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is copper\_crm\_write → convert\_lead. Example data.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/copper-crm-api-mcp-server.md#automations)

## Copper CRM tools this automation uses

__Cotlet Copper CRM tools used to convert qualified Copper leads to people and deals__
| Tool | Parameters |
| ------------- | ---------------------------------------------------------------------------------- |
| list\_leads | status, limit, cursor |
| list\_people | query, limit, cursor |
| convert\_lead | lead\_id, contact\_type, opportunity\_name, pipeline, close\_date, monetary\_value |

[All 12 Copper CRM tools with descriptions](https://cotlet.dev/integrations/copper-crm-api-mcp-server.md#tools)

## Frequently asked questions

### Is it safe to connect Copper CRM to Cotlet?

Yes. You sign in to Copper CRM yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Copper CRM once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

## More Copper CRM automations

- [Find stale Copper deals and create follow-up tasks](https://cotlet.dev/integrations/copper-crm-api-mcp-server/follow-up-on-stale-deals.md)
- [Close lost Copper deals with a loss reason](https://cotlet.dev/integrations/copper-crm-api-mcp-server/close-lost-deals-with-a-reason.md)
- [Copper CRM API and MCP server: every tool](https://cotlet.dev/integrations/copper-crm-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to Copper CRM.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with Copper CRM.

[Sign up free](https://cotlet.dev/app/signup?app=copper-crm)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.