Automation
Webhooks
Webhooks let you fan out accepted lead events into internal APIs, enrichment pipelines, Slack notifications, or bespoke routing services.
Typical Payload Shape
lead-webhook.json
{
"event": "lead.created",
"websiteSlug": "marketing-site",
"formSlug": "demo-request",
"lead": {
"email": "jane@example.com",
"name": "Jane Doe",
"company": "Acme Inc"
},
"metadata": {
"source": "landing-page",
"createdAt": "2026-03-11T12:34:56.000Z"
}
}Best Practices
- Respond quickly with a `2xx` status and move longer work to async jobs.
- Make your receivers idempotent so retries do not create duplicates.
- Log failed deliveries with enough context to replay them safely.
- Keep webhook business logic small; normalize your core lead model in 1DB first.
Core Concepts
Review how forms, leads, and delivery fit together.
HubSpot Sync
Combine CRM sync with webhook-based internal automation.