CRM connectors
Deliver accepted leads to one or more external systems through reviewed recipes.
Deliver accepted leads to up to five active external destinations, each with its own saved configuration, credential, state, and delivery history.
Why it matters
Provider presets shorten setup, while independent connectors keep one destination's result from changing lead ownership or another connector's outcome. When a destination accepts the request, this handoff can reduce manual re-entry and leave operations with a recorded HTTP result to investigate.
Where to work
Open Company -> Connectors. Use New connector to choose a preset, and use Edit to review a connector's provider, saved revision, state, destination, and Delivery history.
Steps
- Select New connector and load the preset for the intended destination.
- Review every prefilled value, then complete the destination, write-only credential, Payload fields, request template, and Successful HTTP statuses.
- Optionally run Test draft with synthetic data to check the values currently visible in the editor.
- Select Create connector, or Save changes when editing, to create the saved revision used by real delivery.
- Review the at-least-once duplicate warning, then Activate the saved connector.
- Accept a new synthetic lead and verify each connector's result separately in Delivery history and, when possible, in the destination.
See it in HoneyFalcon
Connector list with independent status and destination context.
Operate multiple destinations with one clear lifecycle
Start with the destination recipe
Generic webhook, Zapier, Make, HubSpot, Pipedrive, HighLevel, Google Sheets, and Salesforce Web-to-Lead use the same connector workflow with provider-specific starting values. The preset is selected when a connector is created and fixes that connector's provider identity.
For another provider or account boundary, create a separate connector instead of repurposing an existing record.
Review, save, then activate
A preset fills visible configuration but does not save it or supply a customer credential. Test draft is an optional point-in-time request from the visible form. Create connector or Save changes produces the saved revision; Activate makes that saved revision available to real delivery.
Because outbound delivery is at least once, the receiver should deduplicate by the delivery ID supplied by HoneyFalcon.
Keep each result independent
A company can have up to five active connectors. Each connector keeps its own provider identity, credential, saved revision, state, and history.
One connector may record Delivered while another is pending or failed. Those outbound states do not reverse the lead's acceptance inside HoneyFalcon.
Verify the result at the right boundary
Delivered means the destination returned one of that connector's configured Successful HTTP statuses. It does not by itself prove that a contact, person, row, or downstream automation has the intended final values.
During setup, pair HoneyFalcon's Delivery history with a safe read-back in the destination whenever that provider offers one.
A practical rollout
Start with one destination and one synthetic lead. Confirm the saved configuration, activate it, accept the lead through the normal workflow, and compare the HoneyFalcon result with the destination. Add another connector only after the first boundary is understood.
Treat Delivered as the HTTP result recorded by HoneyFalcon. Confirm the contact, person, row, or downstream automation in the destination before considering setup complete.
Your connector setup is ready when
- The intended connector appears in Configured connectors with the correct provider, destination, saved revision, and state.
- The connector can be activated without relying on unsaved editor values.
- A new synthetic lead creates a separate, traceable result for every active connector.
- The destination read-back matches the intended handoff when provider verification is available.