Need help with sfdc-trigger-framework?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

616 Stars 362 Forks MIT License 65 Commits 16 Opened issues


A minimal trigger framework for your Salesforce Apex Triggers

Services available


Need anything else?

Contributors list

# 66,898
55 commits
# 352,701
1 commit
# 245,806
1 commit

SFDC trigger framework

npm version Maintainability

I know, I know...another trigger framework. Bear with me. ;)


Triggers should (IMO) be logicless. Putting logic into your triggers creates un-testable, difficult-to-maintain code. It's widely accepted that a best-practice is to move trigger logic into a handler class.

This trigger framework bundles a single TriggerHandler base class that you can inherit from in all of your trigger handlers. The base class includes context-specific methods that are automatically called when a trigger is executed.

The base class also provides a secondary role as a supervisor for Trigger execution. It acts like a watchdog, monitoring trigger activity and providing an api for controlling certain aspects of execution and control flow.

But the most important part of this framework is that it's minimal and simple to use.

Deploy to SFDX Scratch Org: Deploy

Deploy to Salesforce Org: Deploy


To create a trigger handler, you simply need to create a class that inherits from TriggerHandler.cls. Here is an example for creating an Opportunity trigger handler.

public class OpportunityTriggerHandler extends TriggerHandler {

In your trigger handler, to add logic to any of the trigger contexts, you only need to override them in your trigger handler. Here is how we would add logic to a

public class OpportunityTriggerHandler extends TriggerHandler {

public override void beforeUpdate() { for(Opportunity o : (List) { // do something } }

// add overrides for other contexts


Note: When referencing the Trigger statics within a class, SObjects are returned versus SObject subclasses like Opportunity, Account, etc. This means that you must cast when you reference them in your trigger handler. You could do this in your constructor if you wanted.

public class OpportunityTriggerHandler extends TriggerHandler {

private Map newOppMap;

public OpportunityTriggerHandler() { this.newOppMap = (Map) Trigger.newMap; }

public override void afterUpdate() { // }


To use the trigger handler, you only need to construct an instance of your trigger handler within the trigger handler itself and call the

method. Here is an example of the Opportunity trigger.
trigger OpportunityTrigger on Opportunity (before insert, before update) {
  new OpportunityTriggerHandler().run();

Cool Stuff

Max Loop Count

To prevent recursion, you can set a max loop count for Trigger Handler. If this max is exceeded, and exception will be thrown. A great use case is when you want to ensure that your trigger runs once and only once within a single execution. Example:

public class OpportunityTriggerHandler extends TriggerHandler {

public OpportunityTriggerHandler() { this.setMaxLoopCount(1); }

public override void afterUpdate() { List opps = [SELECT Id FROM Opportunity WHERE Id IN :Trigger.newMap.keySet()]; update opps; // this will throw after this update }


Bypass API

What if you want to tell other trigger handlers to halt execution? That's easy with the bypass api:

public class OpportunityTriggerHandler extends TriggerHandler {

public override void afterUpdate() { List opps = [SELECT Id, AccountId FROM Opportunity WHERE Id IN :Trigger.newMap.keySet()];

Account acc = [SELECT Id, Name FROM Account WHERE Id = :opps.get(0).AccountId];


acc.Name = 'No Trigger';
update acc; // won't invoke the AccountTriggerHandler


acc.Name = 'With Trigger';
update acc; // will invoke the AccountTriggerHandler



If you need to check if a handler is bypassed, use the

if (TriggerHandler.isBypassed('AccountTriggerHandler')) {
  // ... do something if the Account trigger handler is bypassed!

If you want to clear all bypasses for the transaction, simple use the

method, as in:
// ... done with bypasses!


// ... now handlers won't be ignored!

Overridable Methods

Here are all of the methods that you can override. All of the context possibilities are supported.

  • beforeInsert()
  • beforeUpdate()
  • beforeDelete()
  • afterInsert()
  • afterUpdate()
  • afterDelete()
  • afterUndelete()

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.