Insites Docs Instance CRMCRM Webhooks

CRM Webhooks

Last updated on April 11, 2026.

A webhook is an HTTP-based callback function that enables direct communication between web applications. It is distinct from APIs in that it eliminates the need for polling by shifting the communication responsibility to the server, avoiding repetitive client calls to check for events. Webhooks allow one application to send automatic notifications or trigger actions in another application whenever a specific event occurs.

In the CRM, webhooks are essential for tasks such as sending notifications and automating workflows triggered by events like creating or editing contacts or companies. For example, you can use a webhook for a contact creation event to automatically send real-time notifications.

Webhooks are NOT triggered by custom API endpoints, direct GraphQL query updates to the database, and imports.

This document discusses the following topics:

  • Webhook events
  • Updating a webhook
  • Enabling a webhook
  • Disabling a webhook

Webhook events

Webhooks fire automatically when specific events occur in the CRM. Each event corresponds to a webhook that you can configure independently.

EventFires when
Company Created A new company record is created.
Company Updated A company record is modified. This includes changes to standard fields, custom fields, and profile information.
Contact Created A new contact record is created.
Contact Updated A contact record is modified. This includes changes to standard fields, custom fields, and profile information.

Updating a webhook

To update a webhook:

  1. Navigate to the CRM from the main menu.
  2. Select Webhooks.
  3. Select the event you want to modify.
  4. Make your changes.
  5. Select SAVE.

These are the input requirements and descriptions for updating a webhook:

Input LabelTypeRequiredDescription
Enable Webhook Toggle No Enables or disables the webhook.
URL Input Field No The uniform resource locator (URL) used by the webhook to deliver data or trigger actions in a recipient application. A URL is required once a webhook is enabled.
Payload Format Radio buttons No Determines the structure of the data sent in the webhook payload. Only available for 'Company Updated' and 'Contact Updated' webhooks. See Payload Format below.

Payload Format

By default, webhooks send the full contact or company record after every change. For 'Company Updated' and 'Contact Updated' webhooks, you can change this to control how much data is sent with each event, useful for keeping integrations lightweight, reducing processing overhead, or getting precise change data.

The right format depends on how your integration uses the data. If you are triggering an alert or automation that only needs to know what changed, such as a notification when a contact status is updated, 'Changes Only' keeps payloads small and integration logic simple. If your system needs some context around the change without the overhead of a full record, 'Changes with Snapshot' is a good middle ground, useful for syncing contacts to a marketing platform where you need enough information to act without making a follow-up API call. If your integration always needs the complete record, for example a data warehouse that overwrites a row on every update, 'Full Object' ensures nothing is missing.

FormatWhat it sendsBest for
Changes Only Only the fields that changed, including their previous and new values. Automations, alerts, and workflows that only need to know what changed. Lightweight and stable.
Changes with Snapshot The changed fields plus a snapshot of the record at the time of the event. Workflows that need extra context around a change without making a separate API call to retrieve the full record.
Full Object (default) The complete record after the change. Syncing records into another system or data warehouse where the full state is always required.

'Company Created' and 'Contact Created' webhooks always send the full object. Payload Format is not available for these event types.

Enabling a webhook

To enable a webhook:

  1. Navigate to the CRM from the main menu.
  2. Select Webhooks.
  3. Select the event whose webhook you want to enable.
  4. Enable the webhook using the toggle.
  5. Select SAVE.

Disabling a webhook

To disable a webhook:

  1. Navigate to the CRM from the main menu.
  2. Select Webhooks.
  3. Select the event whose webhook you want to disable.
  4. Disable the webhook using the toggle.
  5. Select SAVE.
Have a suggestion for this page?

Didn't quite find what you are looking for or have feedback on how we can make the content better then we would love to hear from you. Please provide us feedback and we will get back to you shortly.