Why Use Branched Flows?
Say you have three different product posts on Instagram. Each post needs a different response:
Post about sneakers → Send sneaker product link
Post about jackets → Send outerwear options with Insta message cards
Post about sale items → Send discount code with a message block
Instead of making three separate automations, you build one automation with three branches. Way cleaner to manage.
How to Set Up Condition Branches
Step 1: Add a Condition Block
After your trigger, add a Condition block to your automation flow.
Step 2: Configure Post ID Conditions
In your condition block, set it up like this:
Condition Type: Only Contacts that match Field: {{comment.postId}} Value: Your specific post ID (like 12345)
For multiple posts, add more conditions:
{{comment.postId}}is 12345 (sneaker post){{comment.postId}}is 67890 (jacket post)
Step 3: Build Different Paths
Each condition gets its own flow path:
Path 1: Sneaker catalog + follow up
Path 2: Jacket catalog + different follow up
Path 3: Default path for any other posts
Where to Find Post IDs
Need the actual post ID numbers? Here's how:
Go to your automation builder
When adding a trigger, you'll see the "Select Publication" screen
This shows all your posts with their IDs
Copy the ID from the post you want to target
The post ID appears right in the publication list - just grab the number and paste it into your condition block.
Real World Example
Let's say you're a clothing brand with these posts:
Summer dress collection (Post ID: 12345)
Winter jacket sale (Post ID: 67890)
General brand post (Post ID: 11111)
Your condition block would look like:
Only Contacts that match:
{{comment.postId}} is 12345 → Summer dress flow
{{comment.postId}} is 67890 → Winter jacket flow
{{comment.postId}} is 11111 → General brand flow
None of these conditions → Default response
Pro Tips for Managing Complex Flows
Use the default path Always include a "none of these conditions" branch for posts you haven't specifically configured yet.
Test each branch Comment on each specific post to make sure the right flow triggers.
Keep it organized Too many branches get messy fast. If you're targeting 10+ different posts, consider breaking into multiple automations instead.
When to Use This vs Separate Automations
Use branched flows when:
Posts need similar but slightly different responses
You want centralized management
The flows share common elements
Use separate automations when:
Completely different use cases (sales vs support)
Very complex flows that would make one automation huge
Different team members manage different post types
Common Gotchas
Wrong post ID format
Make sure you're using just the number, not the full URL or any extra characters.
Condition order matters
Spur checks conditions top to bottom. Put your most specific conditions first.
Missing default path If someone comments on a post you didn't include, they'll hit the default path. Make sure it makes sense.
This approach keeps your automation list clean while giving you the flexibility to customize responses per post. Way better than managing dozens of separate flows.