Apex Triggers

| programming | salesforce |

I worked on the Apex Triggers module on trailhead. Apex triggers are very similar to database triggers (remember those?). I remember in my first job, which was an enterprise healthcare company, our DB was littered with hundreds of triggers that did various actions whenever records were inserted, updated, or removed.

Triggers are a powerful concept, but tend to be very difficult to maintain at a large scale. Especially when you have a large team. I think they are an artifact of the legacy development methodologies. These days most of the actions that triggers used to be responsible for are managed as either a part of the model, or as separate background tasks.

Despite this being true in most modern software development, Salesforce allows you to write triggers in a first class way that do things when records change. I think this is a case where they are still “ok” to use because they remove a lot of the overhead with having to figure out how to keep track of the state of all of your various records.

The best part about Apex triggers is that unlike DB triggers which require you to write your code in an enhanced variant of SQL, Apex triggers allow you to write the code in Apex. This means that you can take full advantage of all of the built in salesforce libraries, as well as making HTTP callouts (the most powerful part of all of this) in a really simple way.

One thing to note is that if you do make HTTP callouts with Apex, you must do so asynchronously.

Apex triggers have a handy access to the context that fired the trigger, including both the old and new state of the affected object.

One great hint that the module gives us is to write our code to support both single and bulk operations. While most triggers that I have written operate on only a single object at a time; there may come a day when I may want to do work on multiple objects at a time. For example, if I was using the bulk API. By writing the code in a way that supports bulk operations (essentially using a for loop) you can reuse the same code in the future rather than having to handle both cases separately.

 

Thank you for reading! Share your thoughts with me on bluesky, mastodon, or via email.

Check out some more stuff to read down below.

Most popular posts this month

Recent Favorite Blog Posts

This is a collection of the last 8 posts that I bookmarked.

Articles from blogs I follow around the net

Pluralistic: Remembrance of proteins past (17 Nov 2026)

Today's links Remembrance of proteins past: People like what they like. Hey look at this: Delights to delectate. Object permanence: BBC's bullshit DRM story; Radical hotel-room coffee independence; Foreclosure map predicts Trump vote; Pinkest pink v Anish...

via Pluralistic: Daily links from Cory Doctorow November 17, 2026

Pumped Up Kicks

ALICE Experiment/CERN A simulated collision of lead ions, showing the spray of generated particles. There are two ways to study the earliest moments of the Universe. One is to peer into the deepest, darkest regions of space. The other is to study the most...

via Brian Koberlein November 17, 2026

Actual curl rewrites in rust

For a long time we have received repeated requests for, or questions about, a curl rewrite in rust. Often as a joke, but also seriously. In this modern world of AIs, we have only been waiting for someone to prove it possible and now it seems we don’t have...

via daniel.haxx.se November 16, 2026

Generated by openring