Retry inconsistency
Different nodes and destinations need different failure rules, creating uneven reliability.
n8n webhook retries
Add verified lead delivery to n8n workflows with one node.
Standardize idempotency, bounded retries, response verification, and delivery receipts across self-hosted and cloud n8n workflows.
A successful automation run is not proof of delivery.
n8n gives teams flexible control, but durable delivery still requires careful retry rules, stable event identifiers, failure workflows, and logs. Those controls are easy to implement differently across projects and hard to explain to a client during an incident.
n8n workflow → LeadProof → CRM, database, or downstream automationReplay duplicates
Manual or automatic workflow replays can send the same lead more than once.
Operational blind spots
Execution history helps developers but is not a portable delivery receipt for clients.
Implementation
Put LeadProof in the delivery path.
Keep the tools that create and process the lead. Standardize only the fragile handoff between them.
Open sandbox instructions →- Use an HTTP Request node to call the LeadProof delivery endpoint.
- Map the source event ID into a stable Idempotency-Key.
- Send the final public HTTPS webhook as destination.
- Persist receipt.id and branch on the verified delivery status.
POST
https://leadproof.jessesay.chatgpt.site/api/v1/leadsAuthorization: Bearer lp_live_your_key
Idempotency-Key: stable-source-lead-id
Content-Type: application/json
{
"destination": "https://your-crm.example/webhook",
"name": "Alex Morgan",
"email": "alex@example.com",
"source": "n8n"
}Questions
What teams ask before adding LeadProof.
Does LeadProof work with self-hosted n8n?
Yes, as long as the n8n instance can call the public LeadProof API and the destination is public HTTPS.
Why not only use n8n retries?
LeadProof provides one delivery contract, idempotency layer, verification response, and receipt across many workflows.
Can the receipt be stored in my database?
Yes. Store the returned receipt ID alongside the source event for support and reporting.
See the gaps in your real workflow.
Get an explainable risk score, prioritized fixes, and the right LeadProof plan.