Webhook intake
Send structured JSON leads into HoneyFalcon with a company-scoped API key.
Let external systems post leads straight into HoneyFalcon over a secured webhook, so demand from your other tools arrives automatically.
Why it matters
The tools that generate demand should not need a human to copy leads across. A webhook endpoint plus revocable API keys lets any external system deliver leads directly and securely, so nothing sits waiting in another inbox.
See it in HoneyFalcon
Step 1 of 3: webhook endpoint, header contract, and required fields without a secret.
Step 2 of 3: visible queued-processing and invalid-or-revoked-key 401 contract.
Step 3 of 3: resulting HoneyFalcon lead.
Receive leads automatically over a secure webhook
Authenticate with a revocable key
Each webhook key carries a human-readable label and a short prefix you can recognize, while the secret itself is stored hashed and never shown again after creation.
If a key is ever exposed, you revoke it and issue a new one; rotation is revoke-plus-generate, so a compromised integration is closed without disturbing the others.
Post a lead and let routing take over
An authenticated request is accepted, queued, and processed into a traceable lead that follows your normal allocation, tag, and cost rules.
An invalid or revoked key is rejected, so only integrations you currently trust can create leads.
Copy the secret when you create a key — it is shown once and stored only as a hash. If you lose it, revoke and generate a new one rather than trying to recover it.
Your webhook intake is ready when
- A request with an active key is accepted and becomes a routed lead.
- A request with an invalid or revoked key is refused, and you can recognize each active key by its label and prefix.