What are Webhooks?

Webhooks in WhatConverts send lead data from WhatConverts to external systems in real time. When a new lead is created or updated, WhatConverts automatically pushes the lead data to a URL you define, allowing you to pass information into your CRM, marketing automation platform, or custom applications without manual intervention.

How Webhooks Work

When a lead is created or updated in WhatConverts, the system immediately sends a POST request containing lead data in JSON format to your webhook URL. This outbound request allows WhatConverts to push data to your external systems in real time, so you can process leads instantly without manually checking the dashboard or relying on scheduled reports.

Types of Webhook Triggers

WhatConverts supports two primary trigger types:

New Lead Trigger: Fires when a new lead enters your account. This trigger sends complete lead data, including contact information, marketing source, device details, and lead-specific fields based on the lead type.

Update Lead Trigger: Fires when an existing lead is modified in your account. This trigger sends the updated fields along with common lead variables, allowing you to keep your systems synchronized with changes made in WhatConverts.

Supported Lead Types

You can configure webhooks to trigger for specific lead types, giving you control over which data gets sent to your systems:

• Phone Calls (completed, in progress, and modified)
• Web Forms
• Chats (completed and in progress)
• Text Messages
• Transactions
• Custom Events
• Emails
• Appointments

Common Webhook Data Fields

Every webhook POST request includes common variables that provide essential lead information:

• Lead identification (lead_id, user_id, lead_type, lead_status)
• Lead analysis data (keyword detection, lead summary, intent detection, sentiment detection, topic detection)
• Timestamps (last_updated, date_created)
• Lead qualification (quotable status, quote_value, sales_value, lead_score, lead_state)
• Account details (profile, profile_id, account, account_id)
• Marketing attribution (lead_source, lead_medium, lead_campaign, lead_content, lead_keyword)
• Device and browser information (operating_system, browser, device_type, device_make)
• Contact details (contact_name, contact_company_name, contact_email_address, contact_phone_number)
• Location data (city, state, zip, country, ip_address)
• Third-party tracking IDs (gclid, msclkid, facebook_click_id, google_analytics_client_id, and others)
• Custom field mappings
• Spam and duplicate indicators

Depending on the lead type, additional fields specific to that type of interaction will be included in the webhook payload.

Set Up Multiple Webhooks

WhatConverts allows you to add up to five webhooks that trigger simultaneously. This enables you to send lead data to multiple systems at once, such as your CRM, analytics platform, and internal notification system.

Test Webhooks

If you want to test webhook functionality but don't have a webhook URL ready, you can use testing services like webhook.site to generate a temporary URL and inspect the data WhatConverts sends.

Security Considerations

Webhook URLs should be secure endpoints capable of receiving and processing JSON POST requests. Ensure your endpoint can handle the data volume and implement proper authentication if needed.

Related Topics

• Set Up Webhooks in WhatConverts
• Receive Phone Call Data with Webhooks
• Receive Web Form Data with Webhooks