In Mailcamp, an automation workflow starts from a single trigger. The trigger is the starting node of the automation canvas, so the standard workflow does not appear to support attaching multiple starting triggers to one automation.
What this means in practice
- Each automation begins with one trigger.
- If you want different entry points, the cleanest setup is usually to create separate automations.
- You can still build more advanced paths inside the workflow by using Wait, Condition, and Operation steps after the trigger.
When to create separate automations
- Create one automation for new contacts joining an audience.
- Create another automation for a date-based event such as a birthday or anniversary.
- Create another automation for an API-triggered or recurring workflow.
How to handle different paths in one workflow
- Start with the single trigger that best matches the main entry point.
- After contacts enter the workflow, use Condition steps to branch them based on behavior or data.
- Use Wait steps to control timing between emails or actions.
- Use Operation steps if you need to update, tag, or copy a contact during the automation.
Example approach
- If you want one welcome workflow for new signups and another for contacts added through an API, create two automations.
- If you want one welcome automation with different paths for engaged vs non-engaged contacts, use one trigger and then split the flow with conditions.
Best practice
- Keep each automation focused on one clear starting event.
- Use a clear internal name so your team understands what triggers that workflow.
- If two automations feel too similar, compare the trigger first before combining logic.