Outbound Integrations
How LeadTale pushes data to your downstream systems.
LeadTale supports two outbound transport patterns for sending contact data to your downstream systems:
1. Direct Webhook
Configure a webhook URL inside LeadTale (Account → Developer Settings → Integrations → Webhook). When you push a list of contacts to the webhook integration, LeadTale POSTs a JSON array of contact objects to your URL.
Trigger: manual list push from the app, or automatic via list automation rules. Method: POST Body: JSON array of contact objects with the fields you mapped at integration setup. Auth: optional — you can configure a static header (e.g., a shared secret) at integration setup.
Use webhooks when you want full control over the payload shape and destination.
2. Zapier
Connect Zapier as an integration (Account → Developer Settings → Integrations → Zapier) to route contacts into any of Zapier's 8000+ downstream apps.
Trigger: manual list push or list automation. Action: contacts arrive as records in your Zap; field mapping is set up inside the LeadTale UI at integration time.
Use Zapier when your downstream system doesn't have a direct LeadTale adapter and you want zero custom code.
Event semantics
Both transports use the same underlying event: contact_push. This is the only outbound event today. There is no separate contact_updated / contact_revealed event stream — outbound is list-push-driven, not data-change-driven.
If you need a richer event stream, request it via support — we track demand for additional outbound events.