What is a Webhook Payload?

The webhook itself is the delivery mechanism; the payload is the contents. A typical lead payload carries an event type, a timestamp, the visitor's captured details such as name and email, any custom fields, an identifier for the conversation, and often the page the visitor was on. Your endpoint receives it, reads the fields it cares about, and does something: creates a CRM record, posts to a channel, starts an automation.

Two practical points. First, treat payloads defensively. Read the fields you need by name rather than by position, ignore fields you do not recognise, and expect the shape to gain new fields over time. Second, respond fast and process later. Acknowledge receipt immediately and queue the real work, because a slow endpoint causes retries and duplicates. Verifying the payload came from where it claims is also worth doing before you act on it.

Clerkzo can fire a webhook alongside email and Telegram notifications when a lead is captured, which is what makes it possible to push enquiries into almost any system without waiting for a purpose-built integration. A webhook is the general-purpose joint in an automation stack, and it survives you changing your mind about your CRM.