Link to your account

To help streamline our login experience, you can now access the Trailblazer Community Groups Platform with your account. Click details and how to link your accounts.

Learn how to make email marketing workflows easier from the CLI with BLDR-SFMC

About this event

Projects like BLDR-SFMC are game changes because they provide pathways for us to collaboratively share and learn.

In this special event Tony Zups will give us a walk through about use cases for BLDR-SFMC. If you want to make your email marketing workflows easier with the command line interface then this is one your will not want to miss.

As a teaser here is what will be covered.


BLDR-SFMC or bldr() is an open-source CLI tool that provides SFMC users the ability to work on Content Builder and Automation Studio assets in their favourite text editor, update assets without having to copy and paste content, and gives you the ability to use your favourite GIT provider for version control.

How can BLDR-SFMC be used?

When working on CloudPages, you can create a base HTML shell for your page and store the body HTML in Content Builder code snippet blocks that can be called in with AMPscript.

If you are working on Automations with Script Activities or complex SQL Queries, bring them to an environment that you are comfortable, with access to any of your stored code snippets and syntax highlighting.

Any mission critical communications/automations can be cloned into their own repositories directly from SFMC and committed to version control. Updates made to the processes will be tracked across your team and be rolled back whenever needed.

Have a complex project that you want to organise and create logical code snippets for easier troubleshooting, you can initiate your Content Builder project, create all of your folders and files, and create them in SFMC with just a few CLI commands.

What's on the BLDR-SFMC roadmap?

  1. Support for creating new sql and script activities for Automation Studio.
  2. Project initiation command so bldr projects do not need to start with cloned assets.
  3. Initial package command.
  4. Gather all cloned assets into a serialised JSON object with valid API payloads.
  5. Identify dependancies across all asset types and add dependency definitions to serialised JSON.
  6. Deploy all dependancies and assets to SFMC.
  7. User Interface/Web Application.

And yes there will be Q&A.

TZ listed is in AEST, use this link for your TZ,6&h=21&date=2022-6-14&sln=7.5-8.5&hf=1&c=1509 

RSVP & JOIN to learn more.

Share with a friend that you know would be interested.


Group Leaders

  • Eliot Harper

    Eliot Harper


    Community Group Leader

  • Jarrett Bush

    Jarrett Bush

    University of Melbourne

    Community Group Leader

  • Matt Cameron

    Matt Cameron


    Community Group Leader

Join your local Trailblazer Community Group, meet other developers & get best practices for building on the App Cloud