An Apex Trigger can be used to automate proceses that aren’t possible to automate with a Workflow. For Salesforce Professional Edition and up, Workflows are available and are powerful tools for doing Field Updates, Email Notifications, and Task Generation. But sometimes they aren’t enough. For example, let’s say you want to set a Checkbox field called “Contacted Account?” on the Account object to “True” whenever a completed Event is logged for the purpose of generating Account-level contact penetration views. This cannot be accomplished via a Workflow on the Event object because of the nature of the Salesforce data model. Events can be associated with Accounts, Contacts, Opportunities or even custom objects, so no clean linkage to Account can be established to support a Workflow. However, an Apex Trigger on the Event object can accomplish this Field Update. You can think of an Apex Trigger as a Workflow on steroids. Because Apex Triggers use custom code/programming language, they usually require someone with a development background to build. But knowing what they do can help equip System Administrators to design solutions for their Salesforce org beyond the standard Admin panel. Just remember, if a Workflow can’t do it, a Trigger may be able to.