Convert Lead
copper.convert_lead
ActionCRM & salesconnection required
Calls the Copper API with the connection's credentials.
Convert a Lead into a Person, and optionally a Company and an Opportunity. Copper deletes the Lead once the conversion succeeds.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Copper
- Secret shape
- the API key, or {"api_key": "…"}
- Config it needs
- user_email, base_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
4 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
lead_id The Copper Lead to convert. | string | Yes | — | — | — |
person Overrides for the Person that will be created, as a JSON object. | object | No | — | — | — |
company Details of the Company to create during the conversion, as a JSON object. | object | No | — | — | — |
opportunity Details of the Opportunity to create during the conversion (name, pipeline_id, pipeline_stage_id, monetary_value), as a JSON object. | object | No | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
person The Person record the conversion produced. | object | — |
company The Company record the conversion produced, or null when none was created. | object | — |
opportunity The Opportunity record the conversion produced, or null when none was created. | object | — |
lead_id The Lead that was converted and then removed. | string | — |
{
"company": {},
"lead_id": "",
"opportunity": {},
"person": {}
}See Convert Lead run in a workflow.
In a technical demo we add the Copper connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.