How Panther Hook works
A visual overview of how a visitor becomes a stored lead and how enabled integrations receive it.
One lead, multiple destinations
A submission is stored first. Outbound deliveries are independent and observable.
- 1Capture the lead through a public form or server API.
- 2Validate and save it in the inbox.
- 3Deliver asynchronously to enabled destinations.
- 4Inspect each delivery without losing the lead.
Destinations run only when configured and entitled. Postbacks depend on eligible events and configuration.
In one minute
Your website or server submits a lead. Panther Hook validates and saves accepted submissions before processing any configured outbound delivery.
Different destinations have their own delivery status and retry history. An external failure does not remove a safely stored lead.
Start with your first formChoose where leads go
Configure email notifications, signed webhooks, and available native integrations per form. Advanced outcome-triggered feedback and postbacks require additional setup and suitable access.
Explore integrationsLearn the terminology
If terms like HMAC, postback, attribution, or delivery retry are new to you, the glossary explains them in plain language.
Open the glossary