Skip to main content

Connect lead storage and reply notifications with webhooks

Send new qualified leads or first replies to a receiver, map fields, and understand delivery status.

Written by Umer Arif

A webhook sends an update from ProspectHalo to another tool. Use this guide if you want new leads or first replies to reach your CRM or automation.

Use an agent’s webhooks to send new lead or reply events to your own receiver or a CRM automation. These are HTTPS connections, not CRM account logins.

Choose the event

  • Lead storage sends newly qualified and verified leads after enrollment. It does not backfill existing leads or send imports that bypass qualification.

  • Reply notifications sends each enrolled lead’s first new reply after the connection is enabled. It does not forward every message or historical conversation.

Set up the connection

  1. Open the agent, then Settings > Integration. Choose Lead storage or Reply notifications.

  2. Choose the CRM destination. Use Custom receiver for your own service. A named CRM still needs a receiving workflow or automation that creates or updates the contact.

  3. Paste a public HTTPS Webhook URL. URLs with credentials, query strings or redirects are unsupported. Private or local destinations cannot receive deliveries.

  4. Choose None, Bearer token or X-API-Key header to match your receiver. For authenticated receivers, enter their secret. Saved secrets are not displayed again.

  5. Under Field mapping, match ProspectHalo fields to your receiver’s names. You can use nested names such as contact.email. Use 1 to 20 mappings without overlapping destination fields.

  6. Review Example JSON payload, turn on Enabled, then select Save lead webhook or Save reply webhook. The switch alone does not save.

Each webhook has its own settings and save button.

Each webhook has its own settings and save button. Sample data shown.

Reply text is shared only if you add its mapping. No phone field is sent. Missing or empty values are omitted, so your receiver must handle leads without an email.

Check delivery

The example payload is a sample, not a test request. After a new eligible event, check Recent deliveries and your receiver’s logs.

Delivered to webhook means the receiver returned HTTP 2xx. It does not confirm that the CRM saved a contact. Check the receiving automation separately. Temporary failures may be retried. Use the stable event ID or Idempotency-Key header to ignore repeats.

Change or stop a connection

Turn Enabled off and save to stop future deliveries. When changing CRM destination, select Save CRM choice first, then configure the new URL and credentials. Changing a URL or authentication method requires the appropriate secret again. Unsaved changes do not replace the active configuration.

Did this answer your question?