Bulk Create Leads

copper.bulk_create_leads

ActionCRM & salesconnection required

Calls the Copper API with the connection's credentials.

Create up to ten Leads in one Copper call and report which of them were created and which Copper rejected, with its per-record error.

Connection

1 field, 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
leads The leads to create, as a JSON array of Copper lead objects (each needs a name). Copper accepts at most ten per request.	array	Yes	—	≥ 1 characters; array of object	[{"email":{"email":"jane@example.com"},"name":"Jane Doe"}]

Every value below is the contract’s own example or default — nothing invented.

{
  "leads": [
    {
      "email": {
        "email": "jane@example.com"
      },
      "name": "Jane Doe"
    }
  ]
}

One shape.

Field	Type	Example
results Copper's raw response array, in the same order as the leads sent.	array	—
created The lead records Copper created.	array	—
failed One entry per rejected lead, with its index, Copper's per-field error message, and the object that was sent.	array	—
created_count How many leads Copper created.	number	—
failed_count How many leads Copper rejected.	number	—
requested_count How many leads were sent.	number	—
partial True when Copper created some leads and rejected others, so the step neither wholly succeeded nor wholly failed.	boolean	—

{
  "created": [],
  "created_count": 0,
  "failed": [],
  "failed_count": 0,
  "partial": false,
  "requested_count": 0,
  "results": []
}

Copper's bulk endpoints answer 200 even when individual records fail, so check failed_count rather than the step status.
Copper rate-limits its bulk endpoints to three requests a second.

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.