After enough SFMC engagements, you start to recognize that Automation Studio builds are mostly combinations of six patterns. Knowing them - plus the trigger and Activity options underneath - lets you scope a new build in 30 minutes.
Here's the reference we hand to every new engineer.
Pick the Starting Source first
Starting SourceTriggerUse whenScheduleFixed clockYou know the run time exactly (daily 8am, Mondays, 1st of month)File DropNew file lands in SFTP folderUpload timing isn't fixedAPIExternal system calls SFMC REST APIReal-time triggered by another system (website checkout, CRM event)
Getting the Starting Source right prevents 80% of reliability issues. Schedule with a file dependency is the #1 source of "ran with yesterday's data" bugs.
Then pick the Activities
ActivityPurposeImport FileRead a CSV from SFTP, write rows into a DESQL QueryJoin, filter, transform, aggregate data across DEs; write result to a DEFilterRefresh a Filtered Group or Filtered DE from a predefined Data FilterData ExtractTurn a DE into a CSV on SFMC SFTPFile TransferMove, encrypt, decrypt, or push files between SFTP locationsSend EmailSend from a DE to an email assetVerificationCheck record count in a DE; halt automation if out of rangeWaitPause before the next step
Most production automations chain 2-5 of these. Keep each automation focused; complex flows become three simpler automations chained via a Parent/Child pattern.
The six patterns you'll use every month
Pattern 1: Daily import + send
The simplest automation. Client uploads file on a dependable schedule, you import and send from it. Use Schedule if the upload time is fixed; otherwise switch to File Drop.
Pattern 2: File drop with encryption
Client delivers encrypted files. File Transfer decrypts into the Safehouse, Import File reads from there, Send Email runs.
Pattern 3: Nightly export to external SFTP
The one we covered in the export post. SQL Query filters the data, Data Extract writes it to SFMC SFTP, File Transfer pushes it to the client's SFTP.
Pattern 4: Production-safe import (with Verification)
Adds a Verification Activity between Import and Send. If the imported row count is out of the expected range, the automation halts and sends an alert instead of emailing bad data.
Pattern 5: Send Log archive
Used anywhere the client needs send history beyond the default 10-day retention. Same pattern works for _Open, _Click, _Bounce.
Pattern 6: Encrypted export
When the client requires PGP-encrypted output. Two File Transfer Activities: one to encrypt the file, one to push it.
Wiring patterns together
Individual automations are composable. A common chained setup on enterprise engagements:
Three automations, separate concerns, each one small and debuggable. Alternative: one monster automation with 15 steps that nobody wants to read. Separate concerns.
Where to put the Verification
Rule of thumb: any automation that ends in a Send Email Activity AND imports from a file should have Verification between them. Files fail in too many ways for the Send to be unprotected.
Takeaway
Every SFMC Automation Studio build you'll ever do is a remix of these six patterns. The Activity list is short, the Starting Sources are three, and most production mistakes come from picking the wrong Starting Source or missing a Verification step. Pin this reference somewhere visible and you'll scope new builds faster than the client can finish describing them.
Architecting an SFMC automation suite? Our Salesforce team ships production-grade Automation Studio pipelines with proper monitoring and error handling. Get in touch ->
See our full platform services for the stack we cover.
