Native integrations
Connect Zapier, Make, Google Sheets, Slack, Telegram, or Discord.
Connect the tools you already use
Each native destination has its own credentials, delivery history and plan rules.
- 1Accept and store the lead.
- 2Fan out only to destinations you enabled.
- 3Track failures independently for each destination.
Shown providers are available integration families, not proof that every provider is enabled for your workspace.
Available providers
Use the form’s Integrations tab for first-class destinations: Zapier, Make, Google Sheets, Slack, Telegram and Discord. Each provider has its own validation and connection requirements.
A successful connection test does not necessarily prove that a production lead has been delivered. Use the delivery history for real outcomes.
Learn each provider
Start with the Panther Hook connection and test controls. For token setup, bot permissions and webhook configuration on each provider, consult the official vendor references.
Official integration guidesCredentials and mapping
Treat webhook URLs, bot tokens and other provider credentials as secrets. They are not generally returned again by normal list/read operations.
Zapier and Make support bounded payload mapping; Google Sheets uses a row/column mapping; notification providers use provider-specific safe messages. Available limits depend on the workspace plan.
