---
title: "Apex triggers from the CRM enrichment package"
slug: "apex-triggers-from-the-crm-enrichment-package"
updated: 2026-03-12T00:14:35Z
published: 2026-03-12T00:14:35Z
canonical: "help.madkudu.com/apex-triggers-from-the-crm-enrichment-package"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.madkudu.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Apex triggers from the CRM enrichment package

APEX triggers: **AccountTrigger** and **LeadTrigger**. These are default **ON** when the managed package is installed, and it is highly recommended that these remain enabled to ensure data is always updated.

The purpose of these triggers is to managed changes to the **Account** and **Lead** object that might require us to re-match and re-enrich a certain record. This includes changes to any of the fields used in matching:

- For Account records:
  - **Name**
  - **Website**
- For Lead records:
  - **Company**
  - **Website**

When a changed is made to the fields above, the APEX triggers will delete the HG matching information included in our own fields on the **Account** or **Lead**. This will then result in a new match either during your next nightly sync, or the next time you click **Sync Salesforce** in the HG Platform.

If you want to disable either trigger, you can do so by editing **HG Triggers Control** located in the **Custom Settings** in your Salesforce org.

A view of the APEX triggers:

![Screen Shot 2024-02-09 at 11.28.55 AM.png](https://assets.usepylon.com/20febf08-2521-4a83-ab15-9ab3d174853c%2F564f4512-6f0b-48ad-b0c8-d1542fa361b9-24000552016781.png?Expires=253370764800&Signature=ZzqTpSLDxc~kyy-Il8QmHWYhKbTnF966EXEsvM-z-eoa9ShldyCfvIdAZ29O-MR3ILsjknGbU8WJF1zvsPlnsQATs~u8-BF2hXgVqE87eYHKdTpYe4TWAsCmfTGZ5d9Nj1tWuNawGv-BziBtJFp1d15u~P7nGc0Ndajc97y5sy3DC0OuVfbCDDu74VAI77PyjRNInA7mJ4jQirhIlk~2HjTv-YczANTFclbp-o1zfsHU7qUmB7zVXbePVbwmjTpB24uARVUI4WxY3ZkIsIcVh6hnQ5KBsev2olrI4COCgxfj-7S62Gv5GnpaOlGlFb06FavIBE5setNe~kM5kKOSCw__&Key-Pair-Id=K3NV4LZ47N8M46)

HG Triggers Control in Custom Settings

![Screen Shot 2024-02-09 at 11.29.49 AM.png](https://assets.usepylon.com/20febf08-2521-4a83-ab15-9ab3d174853c%2Fc80dd2d1-5f1c-446a-92fb-0c3cc6f92939-24000535060237.png?Expires=253370764800&Signature=YtNkHIzFBrBbShuUbbkaIPtnpWTv8lpAj-iXD87ePRGMyib~qP6W~xwhbxgm759zdFdAB8IEvPKisbiVPaudX3zMiq-aGeRC7zVp6NTetwFwtwztvXkWkvFM~MA9QABVbXxZYRlFpFbPV2FZISTRc1Mom1MjYsPaG2KxvK3rRdToxBZij~9oVg-hCJUwTQ~MOLHpKrAr0f2QEJ8f4ml8ezMsC~7nps7lbRl~myx1YyExbgMK3f-0lCPQ825lar2ZCDTpjBEneENeqNVEA0kb3sk1r6GnL76YNpKJBKnq7znnCrKkuCfXrhhBll05c2~zA~tEgTcMrAGBkfIZNWiu6w__&Key-Pair-Id=K3NV4LZ47N8M46)

You'll notice in the screenshot above there are other triggers included in this managed package as well - these are all default **OFF**. These must be either activated or configured in order to work.

For**Enforce User Permissions** - these triggers can be enabled if you want the integration to enforce user permissions. Specifically - if a user changes the Account name, but that user does have access to delete HG records, the integration will not delete data. This primarily covers an edge case and permission control, and is there only if you need it.