Webhooks - Leads

Lead revived

Fired when an expired, churned or rejected lead is reopened. The payload reports the status the lead was restored to, which is not always accepted.

postWebhooklead.revived

Payload

Example payload

{
  "lead": {
    "identifier": "lead-xyz789",
    "company_name": "Lead Company",
    "email": "contact@leadco.com",
    "full_name": "Jane Doe",
    "partner": {
      "name": "Acme Corp",
      "slug": "acme-corp",
      "crm_identifier": "P-A1B2C3",
      "segment": {
        "name": "Enterprise"
      },
      "partner_type": {
        "identifier": "referral",
        "name": "Referral"
      },
      "payment_terms": "net_30",
      "payment_frequency": "monthly"
    },
    "partner_member": {
      "identifier": "pm-abc123",
      "full_name": "John Doe",
      "email": "john@acme.com",
      "role": "Admin"
    },
    "managed_by": {
      "full_name": "Jane Smith",
      "email": "jane@company.com"
    },
    "created_by": {
      "full_name": "Jane Smith",
      "email": "jane@company.com"
    }
  }
}

Response

Webhook received successfully

Changes

Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.