Skip to main content

Respond when things change

Let a change in MyCRM prompt the next step in another system. For supported events, MyCRM can send your integration a notification called a webhook, so it knows there is something to act on.

What this could look like​

A deal changes in MyCRM. A configured notification tells your integration about the change, and it refreshes the relevant information in your reporting system. Your team gets a more current view without manually requesting an update.

The notification starts the workflow; your integration decides what to do next and handles the connection to the other system.

Plan a useful, dependable response​

  1. Choose the event that matters. Describe the business change you want to respond to and confirm that it is available.
  2. Define the next action. For example, update a contact in another system or refresh a reporting record.
  3. Agree what happens when something is delayed. A temporary failure should leave work to recover, rather than an unnoticed gap.
  4. Make repeated notifications harmless. Receiving the same notification twice should not create two copies of the business action.
  5. Choose who monitors the connection. Give someone a way to check delivery and resolve failed work.

Not every change in MyCRM is available as a public event. Notifications also do not grant extra access to records. Confirm the event coverage, record access and delivery arrangements for your integration during onboarding.

Implementation notes for your technical team

Arrange an event subscription with LMG for the relevant records and environment. Then:

  1. Receive notifications at your HTTPS endpoint.
  2. Validate the notification and durably queue the work before acknowledging it.
  3. Use normal API credentials to retrieve permitted current data where needed.
  4. Apply the business action in a way that tolerates duplicate notifications and later changes.

A webhook identifier does not authorise access to the associated record. See webhook events for the payload, receiver guidance for implementation and delivery guidance for recovery. Confirm the deployed delivery configuration during onboarding.