Última actualización
Noviembre 17, 2026
X

CRM Webhook: How It Works, Use Cases, and Setup

Descubre folk el CRM para empresas impulsadas por personas.

A deal moves to “Closed won.” Sales knows. The onboarding team finds out the next morning, after someone remembers to send a message. The CRM was updated, but the work stopped there.

A CRM webhook sends a notification to another system when a specific event happens, such as a contact being created or a deal being updated. A configured workflow can use that notification to alert a teammate, create an onboarding project, or update another application.

The webhook delivers the signal. What happens next depends on the instructions you set up in the receiving system.

This guide explains how CRM webhooks work, where they are useful, and how to build a first workflow that you can test and maintain.

CRM Webhook: Quick Overview

  • A webhook sends event data to a specified URL. It lets another system know that something changed without repeatedly checking the CRM.
  • The receiving workflow performs the action. Getting a notification and successfully creating a task are separate steps.
  • Useful starting points include lead capture, deal alerts, and customer onboarding. Choose one event with a clear next action.
  • Webhooks and APIs often work together. The webhook announces a change; an API request can retrieve details or update a record.
  • No-code setup may be possible. Automation platforms can receive webhooks and connect them to supported actions.
  • Plan for repeated or failed deliveries. Test the final result, prevent duplicate actions, and keep a way to investigate errors.

What Is a CRM Webhook?

💡 A CRM webhook is an automated HTTP request that sends event data to a specified URL when something happens in your CRM. You subscribe to an event, such as a new contact being created, and the CRM notifies the receiving system when it occurs.

For example, you might want a message in your sales channel whenever a new deal is created. The CRM sends the event to an automation platform, which checks the details and posts the message. Nobody needs to copy the information across manually.

Three terms help explain the setup:

✅ Event: The change you want to track, such as a deal update.

✅ Endpoint: The URL where the notification is delivered.

✅ Payload: The information included in the notification, often formatted as JSON.

The payload might contain the changed record’s ID and selected details. It does not necessarily include the full contact or deal history. If the workflow needs more information, it can retrieve it through an API.

Incoming vs. Outgoing CRM Webhooks

The difference is the direction the notification travels.

👉 An incoming webhook brings an event from another tool into a CRM workflow. A website form might send submission details to an automation platform, which then creates or updates a CRM contact. The CRM must support a receiving endpoint, or an integration must handle the request and perform the update.

👉 An outgoing webhook sends an event from the CRM to another system. For example, a deal update can notify a workflow that creates a customer onboarding project.

A single process can use both directions. A form submission creates a contact, then a CRM event triggers a notification to the assigned salesperson.

With folk integrations, the tools and actions you connect determine what the workflow can do. The webhook carries the event; the configured action turns it into useful work.

How Does a CRM Webhook Work?

Say you want to create an onboarding project whenever a deal is marked “Closed won.” The webhook tells another system about the change; your workflow decides whether to create the project.

Here is what happens:

  1. The deal changes in the CRM. A salesperson marks it as won. The webhook is subscribed to the relevant update event.
  2. The CRM sends a request. It delivers event data to the receiving URL, which might belong to an automation platform or your own application.
  3. The receiver checks the event. It verifies the request, confirms that the deal meets your conditions, and retrieves any missing details.
  4. The workflow creates the project. It sends the customer information to your project management tool and records the result.

That third step matters. A general “deal updated” event could fire when someone edits a name or changes an amount. Your workflow needs to identify the relevant status change and avoid creating another project if the same event arrives twice.

Receiving the webhook does not prove that onboarding started. The notification can arrive successfully while the project creation fails because a required field is missing. Check both delivery and the final action.

CRM Webhooks vs. APIs: What Is the Difference?

A webhook tells your system that something happened. An API lets your system request information or perform an operation.

Método Cómo funciona CRM example
Webhook Sends a notification when a subscribed event occurs Reports that a deal was updated
API request Retrieves data or performs a supported action when called Fetches the deal’s current details
Polling Makes repeated API requests to check for changes Checks every few minutes for updated deals

Webhooks and API requests often work together. The notification may provide a record ID, then the receiving workflow uses that ID to fetch the information needed for the next action.

Polling can be useful when the source does not offer the event you need. Its updates depend on the checking interval, while webhook delivery usually starts shortly after the event. Neither approach removes the need to handle failures.

5 Practical CRM Webhook Use Cases

A useful webhook connects a change to something your team would otherwise do by hand. Start with a workflow that has an obvious owner and a result you can check.

1. Capture and Route New Leads

Someone submits a demo request. The form tool sends a webhook to your integration, which looks for an existing contact before creating or updating the CRM record.

The workflow can then assign an owner using territory, company size, or another defined rule. This keeps sales leads moving without someone checking form submissions throughout the day.

→ Check first: What happens when an existing contact submits the form again? Update the relevant record and preserve the new request rather than creating a duplicate.

2. Alert the Right Person When a Deal Changes

A deal enters the proposal stage. A webhook notifies a workflow, which sends the owner a reminder to prepare the agreed documents.

Filter these alerts carefully. A notification for every record edit soon becomes background noise. Choose changes that require someone to act, and include the deal link and expected next step.

→ Check first: Does the event identify a stage change, or only say that the deal was updated? Your workflow may need an additional check before sending the alert.

3. Start Customer Onboarding After a Win

A salesperson marks a deal as won. The receiving workflow checks for the required customer details, creates an onboarding project, and notifies the person responsible.

Include enough context for that person to begin: the customer contact, purchased service, agreed start date, and any commitments made during the sale.

→ Check first: Has an onboarding project already been created for this deal? Store the project ID or another reference so a repeated delivery does not create a second one.

4. Update Marketing Segments

A contact becomes a customer or changes their communication preferences. A webhook can trigger a corresponding update in your email marketing platform.

This helps remove customers from prospect campaigns and keep relevant segments current. The receiving workflow still needs rules for which list memberships or properties to change.

→ Check first: Customer status does not establish marketing consent. Keep subscription preferences separate and avoid automatically resubscribing an opted-out contact.

5. Keep an Internal System Updated

Your team changes a company record in the CRM. A webhook tells an internal application about the update, and the integration transfers the fields that application needs.

This can reduce repeated edits across systems. Decide which application controls each shared field: for example, the CRM might own the account manager, while billing software owns payment status.

→ Check first: Can the receiving update trigger another webhook back to the original system? Add conditions to prevent the same change from bouncing between applications indefinitely.

How to Set Up a CRM Webhook in 5 Steps

For your first webhook, pick something you can check immediately: a deal changes status, and a message appears in your team’s channel. Once that works, you can build on it.

1. Choose the Change You Want to Track

Be specific about the result you want:

When a deal moves to “Closed won,” send the onboarding owner a message with the customer name and deal link.

Look at the events your CRM offers. You might find “deal updated” rather than “deal won.” In that case, you will need a condition later in the workflow to check the status.

2. Get Your Receiving URL

Open your automation platform and create a workflow with an incoming webhook trigger. It will give you a URL to copy into your CRM.

If you are connecting to your own application, a developer will need to provide the endpoint. You can also check the available integrations first—a connector may already handle the event and action you need.

Keep the receiving workflow in test mode while you set it up.

3. Add the Webhook in Your CRM

Paste the URL into your CRM’s webhook settings, select the event, and give the connection a name you will recognize later. “Won deal → onboarding alert” is more useful than “Webhook 1.”

Set up the verification method your CRM supports, then trigger a test event. You should see a request arrive in the receiving tool.

4. Tell the Workflow What to Do With the Data

Open the test request and inspect what arrived. You may have the customer name and deal status, or just an ID that requires an API request to fetch the details.

Select the values for your notification and add the conditions. For this example, the deal must be won and have an onboarding owner.

Also decide how to avoid sending the same alert twice. Depending on the tools, you might track the event ID or record that the onboarding alert has already been sent.

5. Run a Real Test Before Switching It On

Change a test deal in the CRM. Did the right person receive the message? Does the link open the correct record? Is the customer name there?

Try updating an unrelated field, too. That should not send another onboarding alert.

Finally, check where failures appear and whether deliveries are retried. Make sure someone knows where to look when an expected action does not happen!

How to Avoid Common CRM Webhook Problems

The first test worked. A week later, someone gets three onboarding alerts for the same deal—or no alert at all. Before adding more workflows, check how yours handles these situations.

  • ❌ The same event arrives twice. Retries can produce repeated deliveries. Where available, use the event ID to recognize requests you have already processed. For actions such as creating an onboarding project, keep a reference against the deal so it cannot be created again accidentally.
  • ❌ The receiving tool is unavailable. Check your CRM’s retry policy rather than assuming it will keep trying. Make failed deliveries visible and establish how to replay them once the connection is working again.
  • ❌ An older update arrives after a newer one. Delivery order is not always guaranteed. Use timestamps or version information where supported. If the action depends on the record’s current status, retrieve it before proceeding.
  • ❌Two systems keep triggering each other. A CRM update changes another application, which sends an update back to the CRM. Define which system controls each shared field and skip updates when the value has not changed.
  • ❌ The endpoint accepts requests without verification. Use HTTPS and validate incoming requests with the authentication or signature mechanism your provider supports. Keep credentials out of URLs and shared screenshots.
  • ❌ Delivery succeeds, but the action fails. The endpoint can receive a request while the next step fails because a field is missing or a connection has expired. Check the final action in your workflow logs, and alert the owner when it cannot be completed.

Keep a short record of what triggers each workflow, who owns it, and where failed runs appear. That is usually enough to make troubleshooting much quicker.

Connect CRM Events to Your Workflows With folk!

A deal changes in folk. Your onboarding team needs to know, or another application needs the updated information. Webhooks let you pass that event to a receiving workflow without waiting for someone to copy it across.

folk supports webhook notifications for events involving people, companies, and deals. You choose the events to subscribe to and provide the URL that will receive them.

For an onboarding alert, the setup could look like this:

  1. A deal is updated in folk.
  2. Your receiving workflow checks whether it meets the “Closed won” condition.
  3. It retrieves any additional information needed.
  4. It sends the onboarding owner a message with the customer details and deal link.

You can build the receiving workflow using a compatible automation platform or your own application. The folk integrations page is a useful starting point for choosing how to connect your tools.

folk sends the event notification; your integration handles the conditions and actions that follow. Start with one useful connection, test it, and check that repeated deliveries cannot create duplicate work.

Try folk to connect CRM updates with your team’s next steps!

Conclusión

Pick one moment where work tends to stall between tools: a new lead waiting for assignment, a won deal waiting for onboarding, or a customer update someone has to copy manually.

A CRM webhook can connect that change to the next action. Test the result, account for repeated deliveries, and make failures easy to find before adding more workflows.

Preguntas frecuentes

What is a webhook in a CRM?

A CRM webhook sends event data to a specified URL when something happens, such as a contact being created or a deal being updated. The receiving application uses that notification to run a configured action.

What is the difference between a webhook and an API?

A webhook notifies another system when an event occurs. An API lets a system request information or perform an operation. They often work together: a webhook reports a deal update, then an API request retrieves the details needed for the next action.

Can you set up CRM webhooks without coding?

Yes, if your CRM and automation platform support the required events and actions. The platform can provide the receiving URL and tools for mapping fields. You still need to configure conditions, check incoming data, and test how the workflow handles errors.

Do webhooks keep two systems fully synchronized?

Not by themselves. Webhooks report subscribed events, but the receiving workflow must apply the changes. Full synchronization also requires rules for matching records, handling deletions, resolving conflicts, and recovering missed updates.

What happens when a CRM webhook fails?

It depends on the provider’s delivery policy. Some retry failed requests; retry schedules and limits vary. Check delivery logs and the receiving workflow’s history. A notification may arrive successfully while a later action fails, so inspect the final result too.

Does folk support webhooks?

Yes. folk supports webhook notifications for events involving people, companies, and deals. You can configure subscriptions and a delivery URL, then use a receiving workflow to send notifications, update another system, or trigger other supported actions.

Pruébal gratis