In marketing ops, controlling the order of operations matters. Some actions have to happen in a specific sequence, and that’s where executable campaigns come in. They give you control, making sure steps run in the correct order, without overlaps.
Imagine a new lead fills out a contact form. You need to set the lead source, enrich the record with company information, and then route the lead to the right rep before syncing to Salesforce. Without the right sequence, you risk routing the lead on incomplete or inaccurate data, and your process breaks down straight away.
Executable campaigns split your process into distinct steps, each run in the right order. When triggered by the Execute Campaign flow step, the parent campaign pauses and waits for the executable to finish before continuing. Every task is completed in the correct sequence, every time.
Executable campaigns vs requested campaigns
Both are invoked by a parent campaign, but they handle execution differently.
A requested campaign runs asynchronously. The parent campaign doesn’t wait for it to finish; it sends the request and carries on. That creates parallel processes, which are useful in some cases but can cause painful timing issues or steps running out of order.
An executable campaign enforces strict sequencing. The parent pauses until the executable completes, then moves to the next step. That makes executables ideal when enrichment, routing or CRM syncing must happen in a specific order, without overlap or risk of error.
What to watch out for with executable campaigns
Executable campaigns are incredibly useful, but there are a few important caveats.
The setting can’t be changed later
Once a campaign is marked as executable, it can’t be switched back. If you forget to select it when you create the campaign, you’ll need to clone or recreate it. Not the end of the world, but worth knowing.
No waits or webhooks inside
Executable campaigns run straight through. Any pauses or external API calls need to happen in the parent campaign, or through a custom flow action.
Same workspace only
The parent and executable campaigns must be in the same workspace. You can’t invoke an executable across workspaces, so organise your campaigns with that in mind.
Three levels of nesting
You can chain up to three levels of executable campaigns: parent, child and grandchild. Anything beyond that won’t run, so plan your structure around the limit.
Be careful with “Remove from Flow”
Using Remove from Flow inside an executable removes the person from every active campaign in the chain, not just the current one. Double-check it so you don’t pull people out of other campaigns by accident.
Questions about executable campaigns? Email david@martechulate.com.