Update Lead
Leads
Update Lead
Update a lead’s metadata and optionally transition to a new state
POST
Update Lead
Overview
Asynchronous Endpoint: This endpoint queues the lead update for background processing and responds immediately. The actual outcome of the update will be sent via webhook callbacks configured in your Process.
Body Parameters
MongoDB ObjectId of the lead (required if not using referenceId)
External reference ID (requires projectId and processId)
Required when using referenceId
Required when using referenceId
Metadata object to merge with existing metadata
Update the lead’s name
Target state to transition the lead to (e.g., “interested”, “lost”, “followup_2”)
Disposition reason (used with targetState “interested” or “lost”)
User ID for audit logging
If
metadata is not provided, all other fields (except leadId, referenceId, projectId, processId, targetState, name, disposition, userId) will be merged into metadata.Response
Indicates if the update request was successfully accepted
Confirmation message (e.g., “Lead update initiated”)
Webhook Notifications
Once the asynchronous update job finishes processing, a webhook will be sent to the callback URLs configured in the Lead’s Process.- Success Payload
- Failure Payload
This payload is sent when the lead is successfully updated and transitioned (if requested).
