Generic webhook connector
Deliver a controlled HoneyFalcon payload to a customer-owned HTTPS endpoint.
Deliver accepted lead data to a customer-owned HTTPS endpoint with an explicit field allowlist, request template, authentication options, and accepted status set.
Why it matters
A generic webhook lets a compatible destination join the same outbound workflow without a provider-specific HoneyFalcon integration. Payload fields limit what the connector may send, while write-only credentials and optional signing keep reusable secrets out of the visible template.
Where to work
Open Company -> Connectors, select New connector, choose Generic webhook under Destination type, and select Load preset.
Steps
- Load the Generic webhook preset and review every prefilled value.
- Enter a clear Connector name and the receiver's final public HTTPS Destination URL.
- Choose the payload format and keep Successful HTTP statuses limited to responses the receiver legitimately returns after accepting the request.
- Add a write-only Credential only when the endpoint requires one, and enable HMAC signing only when the receiver validates the signature.
- Select the minimum Payload fields needed by the destination, then use only those field placeholders in custom headers and the request template.
- Run Test draft with synthetic data, then Create connector or Save changes and Activate the saved revision.
- Accept a new synthetic lead and verify the separate result in Delivery history and at the receiver.
See it in HoneyFalcon
Step 1 of 4: Generic webhook preset selected in the connector editor.
Step 2 of 4: Generic webhook destination and protected credential controls.
Step 3 of 4: Generic webhook Payload fields using the shared generic mapping.
Step 4 of 4: Generic webhook endpoint and Successful HTTP statuses to review before creation.
Build a webhook contract the receiver can verify
Use the preset as a reviewed starting point
Generic webhook preloads a JSON request pattern and common successful statuses. Loading the preset replaces visible unsaved values; it does not save the connector or provide a credential.
Use this destination type only for an endpoint whose request and response contract you control or can verify.
Send only the fields the destination needs
Payload fields are the connector's allowlist. Every lead placeholder referenced by the payload template or custom headers must be selected there.
Start with the smallest useful set. Add sensitive or extra fields only when the destination has a documented business need and the operator accepts that data scope.
Keep authentication out of visible templates
Use the write-only Credential field and the supported secret placeholder when the receiver expects a token. Use the separate signing secret only when HMAC signing is enabled.
Do not paste a reusable secret directly into the payload template or a visible header value.
Use a public, stable destination
HTTPS is the normal destination. HoneyFalcon rejects unsafe local, private, link-local, embedded-credential, and prohibited redirect targets.
If an explicitly trusted receiver requires insecure HTTP, review that exception deliberately instead of treating it as the default.
Separate the draft test from real delivery
Destination accepted the test means the visible draft received one of its configured successful HTTP statuses at that moment. It does not save or activate the connector.
Only a separate accepted lead sent through the saved active revision creates Delivery history. Confirm the receiver's own result before considering the integration complete.
Example: connect an internal intake service
An operations team can select contact and source fields, map them to the receiver's JSON names, sign the body with HMAC, and accept only the documented 2xx statuses. HoneyFalcon then records each real outbound result without requiring a provider-specific recipe.
Use a public HTTPS destination and select every lead field referenced by the payload or headers. Keep reusable secrets in the write-only credential or signing fields, never in visible templates.
The webhook contract is ready when
- The destination URL, payload format, selected fields, template placeholders, authentication, and Successful HTTP statuses match the receiver's documented contract.
- Test draft with synthetic data returns an expected status without saving or activating the form.
- The saved connector can be activated without unsaved values.
- A separate synthetic lead produces a traceable Delivery history result and the receiver can verify the expected data.