Perhaps you haven’t heard about Automation Studio’s script activity yet? Or maybe you’re still wondering what you can do with it. You’re not alone, as this powerful activity type’s sorely underused. However, you’ll appreciate its flexibility and power once you see what it can do. Many MVPs, Marketing Champions, and passionate power users swear by these activities and utilize them for complex situations otherwise requiring external software solutions.
You can find script activity in the “Activities” section of Automation Studio and add it to the automation workflow just like any other activity.
While it is a “Script Activity” and should therefore be clear to Marketing Cloud that it contains SSJS code, you must use a script-tag within the activity configuration just as you would on a CloudPage to indicate where the SSJS code is located:
But what exactly can I do with it?
Here are some examples of how you can use script activity:
- Interact with the Marketing Cloud API or SSJS Marketing Cloud functions to:
- Trigger other automations or activities within an automation. Run them on demand or as soon as a task is finished rather than the typical schedule.
- Dynamically create data extensions based on data fetched using your script.
- Initiate the contact deletion process.
- Interact with external APIs:
- Fetch data from a blog via API and write it to a data extension to send a fully automated newsletter.
- Perform batch updates in Sales and Service Cloud using the Salesforce Bulk API to optimize for performance and avoid mass updates from Journeys or CloudPages.
- Connect external services (print providers, snail mail providers, custom push or SMS, etc.).
- Fetch key metrics or data required for personalization using an API to avoid heavy API use within emails. Avoid using integration middleware for minor data points (e.g., number of current auctions at an auction platform, the number of job offers for a career page, etc.)
What if something goes wrong?
First, every time an error is thrown, the automation will fail; thus, the activity will show as failed. No further steps will run automatically. Unfortunately, the error message isn’t displayed anywhere in Automation Studio. That’s where you must be prepared to step up your debugging game: Create a log for your error messages.
Create a data extension as an error log and catch any errors using try-catch, logging the message, and then throwing the error again. Hence, the automation still fails if an error occurs (this step is essential because otherwise, the activity will be seen as successful by the system).
Here’s what such an error logging code would look like:
You can also add custom error codes if you’re writing longer scripts with custom checks that throw errors for invalid input data, etc. That’s the beauty of SSJS activities; you’re free to extend and customize to fit your needs!
The great flexibility that comes with Script Activities (and Custom Activities for Journey Builder, for that matter) might just be what sets Salesforce Marketing Cloud apart from its competition. So if you have a requirement that seems unsolvable, think again and consider using a script activity.