Webhooks are the universal glue of the modern web — HTTP POST callbacks that fire from one system to another when an event happens. Connecting webhooks to WellPlan lets any tool that can send an HTTP request push data into the CRM, and lets WellPlan workflows push data out to any tool that can receive one. Inbound webhooks become triggers; outbound webhook actions become integrations with anything custom. Combined with the visual workflow builder, webhooks turn WellPlan into a flexible automation hub even for tools that do not have a native integration listed.
Features
Common use cases
Catch leads from a custom landing page
A startup runs a bespoke marketing site without a standard form provider. The site POSTs each submission to a WellPlan webhook URL, which creates the contact, applies tags, and starts a welcome sequence — no custom CRM code required.
Notify external systems on CRM events
An e-commerce brand fires an outbound webhook to its warehouse management system whenever a deal in WellPlan moves to Paid. The payload carries the order ID, items, and shipping address so the warehouse can pick and ship within minutes.
Bridge tools without a native integration
An agency wires a niche industry tool to WellPlan using webhooks at both ends. The tool sends events to a WellPlan inbound URL, and WellPlan posts back to a custom endpoint on completion, replacing what would otherwise be a manual sync.
How setup works
- 1In WellPlan's workflow builder, add a Webhook trigger to generate a unique inbound URL.
- 2Configure the sending system to POST JSON payloads to that URL on the event you want to capture.
- 3Map the incoming payload fields to contact properties, custom fields, and workflow variables.
- 4For outbound calls, add a Webhook action with the target URL, method, headers, and JSON body, then test end-to-end.
Frequently asked questions
What content types are supported?+
Inbound webhooks accept JSON, form-encoded, and most common content types. JSON is by far the easiest to work with because the payload maps cleanly to nested fields inside the workflow. Outbound webhook actions let you set the Content-Type header explicitly.
How do I secure my webhook endpoints?+
Each inbound webhook URL contains a unique token in the path, which acts as a shared secret. You can additionally require a custom header value or signature, and validate the source IP if your sending system uses a fixed range.
Can webhooks include authentication for outbound calls?+
Yes. Outbound webhook actions support Bearer tokens, Basic auth, custom headers, and signed payloads. This is enough to integrate with most REST APIs that require an API key or token, without writing custom code.
What happens if the receiving server is down?+
Outbound webhook actions can be configured with retries and timeout values. Failed deliveries are logged in the workflow run history, where you can inspect the request and response and re-run the step manually after the receiving system is back online.