Connect Zapier
Send accepted HoneyFalcon leads to a Webhooks by Zapier Catch Hook.
Start a Zapier workflow when HoneyFalcon sends an accepted lead to a customer-owned Webhooks by Zapier Catch Hook.
Why it matters
The Zapier preset turns one accepted lead into a structured webhook that can continue into the tools already used by sales and operations. HoneyFalcon keeps the routing and HTTP delivery record, while Zapier owns every action after the Catch Hook.
Where to work
Create the Catch Hook in Zapier first. Then open Company -> Connectors in HoneyFalcon, select New connector, choose Zapier webhook, and select Load preset.
Steps
- In Zapier, create a Zap with Webhooks by Zapier and choose Catch Hook as the trigger.
- Copy the unique Catch Hook URL and keep it private.
- In HoneyFalcon, load the Zapier webhook preset and paste the Catch Hook URL into Destination URL.
- Review Payload fields, the JSON request template, and Successful HTTP statuses; a HoneyFalcon credential is normally not required.
- Run Test draft with synthetic data while Zapier is ready to receive a sample.
- Confirm the sample in Zapier, configure the downstream actions, test them there, and publish the Zap.
- Create connector or Save changes, Activate the saved revision, then accept a new synthetic lead and verify both Delivery history and the Zap run.
See it in HoneyFalcon
Step 1 of 3: Zapier preset selected in the connector editor.
Step 2 of 3: Zapier destination and protected credential controls.
Step 3 of 3: Zapier endpoint and Successful HTTP statuses to review before creation.
Connect the Catch Hook without confusing two results
Create the receiving trigger first
Zapier supplies a unique Catch Hook URL for the trigger. HoneyFalcon does not create or publish the Zap, so prepare that receiving URL before completing the connector.
Treat the URL as sensitive operational configuration. Do not place it in screenshots, tickets, or public documentation.
Review the preset as a starting point
The preset supplies a JSON payload pattern and common successful statuses. It does not save the connector, publish the Zap, or insert a credential.
Keep only the Payload fields required by the Zap. When the Zap needs a different field name, change the JSON mapping while keeping every referenced HoneyFalcon field selected.
Capture a synthetic sample
Run Test draft while Zapier is waiting for a sample. Destination accepted the test means the Catch Hook returned an allowlisted HTTP response for the visible draft.
Use that synthetic sample to map Zapier actions. The test does not save or activate the HoneyFalcon connector and does not create Delivery history.
Publish and verify both sides
Complete and publish the downstream Zap separately. Then save and activate the HoneyFalcon connector and accept a new synthetic lead through the normal workflow.
Check Delivery history for HoneyFalcon's HTTP result and Zap history for trigger and action results. A Delivered record does not prove that every downstream Zap action completed.
Keep the Catch Hook URL private. HoneyFalcon records the hook's HTTP response; verify the trigger and every downstream action separately in Zapier.
The Zapier handoff is ready when
- The connector uses the intended Catch Hook URL and the smallest useful Payload fields.
- Zapier captures a synthetic sample whose fields match the intended mapping.
- The Zap is published independently of the HoneyFalcon connector.
- A new synthetic lead has a traceable HoneyFalcon delivery and a corresponding successful Zap run.