Duplicate Leads
A retried source event can create the same company or contact more than once when the original Close response is lost.
Close CRM lead delivery
Make every captured lead become the right Close CRM record once.
Protect Close-bound lead and contact creation with approved field mapping, stable source identity, duplicate-safe retries, destination verification, and delivery receipts.
Paid plan uses secure Stripe checkout · plan assigned after verified payment · activate with the checkout email- 25live deliveries
- 14 daysproduction access
- No cardto start
- Real APInot a demo
A successful automation run is not proof of delivery.
A form, booking, or AI conversation can finish successfully while the Close API write times out, rejects a field, or is replayed into a duplicate Lead. The source tool usually cannot prove which Close record was accepted.
Form, booking, or AI agent -> LeadProof -> authorized Close CRM lead endpointBroken field mapping
Deprecated custom-field shapes or invalid status values can reject a record after the capture workflow appears complete.
No portable receipt
The originating workflow needs a stable delivery outcome it can store without retaining full lead payload history.
Implementation
Put LeadProof in the delivery path.
Keep the tools that create and process the lead. Standardize only the fragile handoff between them.
Platform reference: Close API: create a Lead ↗Open sandbox instructions →- Verify the source event and map only the approved Lead and nested Contact fields.
- Derive one Idempotency-Key from the original form, booking, call, or conversation ID.
- Send the normalized payload through LeadProof to the authorized Close lead-creation integration endpoint.
- Store the LeadProof receipt ID and branch on delivered or delivery_failed before downstream sales automation continues.
POST
https://leadproof.jessesay.chatgpt.site/api/v1/leadsconst sourceEventId = payload.event_id;
const response = await fetch(
"https://leadproof.jessesay.chatgpt.site/api/v1/leads",
{
method: "POST",
headers: {
Authorization: `Bearer ${process.env.LEADPROOF_API_KEY}`,
"Content-Type": "application/json",
"Idempotency-Key": sourceEventId
},
body: JSON.stringify({
destination: "https://integrations.example/close/leads",
name: payload.name,
email: payload.email,
phone: payload.phone,
source: "close_crm"
})
}
);
const delivery = await response.json();
if (!response.ok || delivery.receipt?.status !== "delivered") {
throw new Error(
`Close delivery failed: ${delivery.receipt?.id || "no_receipt"}`
);
}Questions
What teams ask before adding LeadProof.
Does LeadProof store the Close API key?
No. Keep Close authentication inside the authorized integration endpoint or secret manager. LeadProof receives the public HTTPS destination and delivery payload, not the Close credential.
Should I create a Close Lead or Contact first?
Close allows contacts to be nested when a Lead is created. Choose the approved mapping for the workflow, keep it consistent, and use one durable source event ID for retries.
Can I use Close custom fields?
Yes. Map only approved custom field IDs and avoid deprecated name-based or nested custom-field formats described in the current Close API documentation.
See the gaps in your real workflow.
Get an explainable risk score, prioritized fixes, and the right LeadProof plan.