There are times when we need to integrate both Automation Studio and Journey Builder like sending an email to a set of audience after running a script in a data extension. There are some reasons we need Journey Builder and not Automation Studio to send email:
- Utilizing the Splits – Decision, Random, Engagement
- Do some updates to the connected SFDC environment like creating a task or a case or updating an object.
However, we cannot execute a script or run an SQL query in Journey Builder. Say, to clean up the Data Extension or merge the Data Extensions before sending the bulk email. In such cases, we may need to rely on the Automation Studio and then call the Journey Builder upon these activities gets completed.Continue reading “Marketing Cloud : Trigger Journey Builder From Automation Studio”