Deliver prospects to CRMs and signed webhooks

Use connected native CRMs or a signed HTTPS endpoint as ordered destinations.

When to use this

Use native CRM delivery for supported accounts and webhooks when your own HTTPS endpoint should receive versioned prospect.created events.

Native CRM destinations must show Connected.
Webhook URLs must use HTTPS and cannot be private, local, credentialed, or use a non-standard port.
Free can add one webhook endpoint for $5 per month; Grow and Scale include webhooks.
Save a new or rotated signing secret immediately; it is shown once.

Connect the CRM, or choose Webhook Set up.
For a webhook, select Create webhook, enter Name and HTTPS URL, and choose Enable after saving.
Save the signing secret outside the page.
Select Test and open History to inspect the result.
Create a Delivery workflow and add connected destinations in the intended order.

Controls in Leama
Control	What it does
Name	A recognizable endpoint name.
HTTPS URL	The public receiver for signed prospect.created events.
Test	Queues a test; History shows the result.
History	Shows attempt, HTTP status, latency, safe response excerpt, and retry state.
Rotate secret	Invalidates the old secret for new deliveries and shows a replacement once.
Pause / Enable	Stops or resumes new events while keeping history.
Retry now	Reuses the original event identity and uses no additional prospect credit.

History shows Pending, Retry scheduled, Delivered, or Failed. A successful test proves only that attempt.

Customer-visible states
State	Meaning
Active	The endpoint can receive new events.
Inactive	Settings and history remain, but no new event is sent.
Entitlement disabled	The plan or add-on does not allow delivery.
Pending	The attempt has not completed.
Retry scheduled	Another automatic attempt has a future time.
Delivered	The endpoint accepted the attempt.
Failed	The attempt ended without delivery.

Retries use no additional prospect credit. Webhook and CRM entitlement charges are separate from run credits.

Problems and next steps
Problem	What to check
The URL is rejected	Use a public HTTPS endpoint with no embedded credentials and a standard port.
The secret was not saved	Rotate it, update the receiver, and save the replacement.
A test was queued but not received	Inspect History rather than assuming delivery.