Apr 1, 2015
New Automation Workflows and API Functionality
More than 115,000 customers use MailChimp’s marketing automation. And 23,000 of them have created automated workflows since last August. That’s a lot of growth! But it’s also a lot of emails—in the past 6 months alone, we’ve sent more than 200 million automated messages. While MailChimp automation already offers a robust feature set, with that kind of volume, we’re excited to keep innovating. Our new release gives automation users more power and control, and sets the stage for even bigger things to come in the future.
With version 3.0 of MailChimp’s API continuing in open beta, we’re pleased to announce the debut of its marketing automation functionality. As we near full feature parity on API 3.0, we wanted to give our growing automation customer base access to the new functionality a few weeks early. We’ve also added 2 new features that have been in popular demand: List Group and Subscription Date Workflows. These features are rolling out with our new release, and will be available for all MailChimp users by the end of the week. Let’s take a look at each of these new additions and see what future API updates have in store.
API workflow
Our new API workflow allows you to bring a much greater level of customization to your automated emails. First, you can now trigger a series of emails on a single API request for a particular subscriber. For example, after submitting a subscriber’s email to the URL in the screenshot above, the automation email "Shopify for MailChimp Update" will immediately queue and send.
Where previously you could only trigger emails with engagement events like open and clicks, now you can trigger a workflow email based on pretty much anything, including e-Commerce webhooks, Wistia video player events, and CRM profile updates. We’ve effectively brought transactional email support to our automation platform.
You can also trigger individual workflow emails on an API request. Now, not only can workflows be started via the API, but each subsequent workflow email can be triggered through a different API call. Where previously you could only trigger emails with engagement events like open and clicks, now you can trigger a workflow email based on pretty much anything, including e-Commerce webhooks, Wistia video player events, and CRM profile updates. We’ve effectively brought transactional email support to our automation platform, and this will let you to build more personalized emails. There’s a tremendous amount of power hidden in this little feature, and we can’t wait to see what you do with it. Frankly, we think it sounds pretty API-tizing.

Other new workflows
We’ve also added List Group workflows, which allow you to send targeted emails based on users joining or leaving particular groups. This will allow you to deliver more relevant content to your subscribers as their interests change. You also have the option to send based on a user’s subscription date. You can use this new functionality to more precisely deliver targeted emails to subscribers who’ve been on your list for several years, or new folks who have just joined.

Looking forward
Next up on our automation to-do list? Getting campaign creation into API 3.0. Until then, you can still build API workflows in the web application, with sending triggers fully functional. We expect plenty more updates to API 3.0 in the next few weeks, including campaign creation. In the meantime, check out our current documentation for a full list of supported commands.
Diogo
Hello, looking forward to mailchimp API, in my opinion something is not right with MC, and i believe most internet marketers agree 100% with me.
Example, infusion soft and others tools you can tag people in multiple lists, in mc you cant :/
yYour lists don’t communicate with the others, makes no sense at all.
and other thing very important, the automation neve stop… we should have a option to say, with de lead does that action stop the automation right now, but is not how it works… why got in touch multiple times in the past year about that subjects with mc, and always the support say “i will pass it forward” i see many releases but never related to that issues that im sure put many people out of MC, these should be standard in every autoresponder tool..
Do you have anything to say about that Chris?
keep rocking!!
by the way I love MC, and your support are far the best and more polite on the internet, but I reall want a straight answer about those issues.
king regards
04.01.2015
Chris MailChimp
Hey Diogo,
As for your comments on greater control for your Automation Queue, that is a high priority for us in the near term. First step was allowing you to add subscribers to your queue, next steps will be removing subscribers from a workflow all together or skipping individual child emails in a workflow. Thanks for your patience as we slowly scale the power of our Automation platform to ensure we do not loose usability.
Towards your list comments, having a Master (single) List and utilizing List tools like Groups and Static Segments is our comparable solution.
By the way, we love you! Thanks for the compliments and criticism, we are glad to hear both.
Thanks,
Chris
04.01.2015
Bjoern Sjut
I think the main downside in regards to other solutions that have “several lists” is that the unsubscribe mode in MailChimp will always unsubscribe a user from the whole list – not from segments.
So in terms of user retention, the MailChimp approach is a bit more risky and offers less control than other solutions.
It would be great, if the unsubscribe link could be customized towards the user can unsubscribe from certain emails within a list (i.e. remove himself from segments). I realize that this would be a difficult usability challenge.
05.04.2015
Chris MailChimp
Hey Bjoern,
Our solution for the global list unsubscribe process you have described above is the “update profile” link. This allows your subscribers to choose exactly what kinds of emails they wish to receive from you.
Thanks!
Chris
05.05.2015
Jonathan
“As for your comments on greater control for your Automation Queue, that is a high priority for us in the near term.”
I want to echo Diogo’s sentiments. I think it’s telling that the first comment on this blog post is about this functionality. In the GUI first, and API second. Without this functionality, Automation is crippled at best, and self-sabotaging for people who don’t realize how it works until it’s too late.
06.17.2015
Chris MailChimp
Thanks for the feedback!
Chris
07.08.2015
Jason Pelker
Did you lose a lot of marketing customers over the last five years to Infusionsoft, AWeber, and then Drip and ConvertKit? I’m genuinely curious how the rise of the automated email system affected your own bottom line.
I’m also interested in whether or not MailChimp uses complex automated email campaigns in their own marketing efforts. Are you eating their own dog food, so to speak?
04.02.2015
Chris MailChimp
Hey Jason,
We designed Automation Workflows to give access to marketing automation to everyone. Our #1 automation campaign for MailChimp is “Merge Field Changed” Custom Workflow. We find simpler is better, and that the best marketing is talking about awesome stuff which we already built.
In reference to your first comment, we are doing well and excited at the growth of our Automation platform. Best wishes going forward!
Chris
04.02.2015
Jonathan
“Our #1 automation campaign for MailChimp is “Merge Field Changed” Custom Workflow.”
If that’s the case, why not focus on other basic functionality (e.g., being able to remove someone from a workflow or add them into the middle or skip certain child emails)? That would be much more helpful than more workflow types.
Due to the lack of basic functionality, I have had to come up with hacks to try to get things working in a useful way. For example, I have dozens of Automation Workflows with 1 email in each, instead of a few workflows with multiple emails in each; and I want to change the trigger in order to work slightly differently, but I have to duplicate them all in order to be able to ensure the people who have received some of the emails receive the rest, and new people go into the new workflows. The result is a lot of wasted time.
06.17.2015
Chris MailChimp
Hey Jonathan, all great points. We are working towards this functionality.
07.08.2015
Binh
I love this new api triggered workflow. When can I expect it to be out of beta? And how do I turn it on on my account?
04.15.2015
Chris MailChimp
Hey Binh, the API Workflow is available to all our Automation customers. Automation is a paid feature and plans start at $10 per month. In terms of API v3.0 beta, we hope to finalize the rest of the API within the next few months. With that said, the Automation endpoints are set and fine to build on with certainty they will not change.
Thanks,
Chris
04.15.2015
Erwan B
“We’ve effectively brought transactional email support to our automation platform, and this will let you to build more personalized emails.”
This statement is not really true: If a user chooses to unsubscribe from MC, they will not get any automations, whether triggered from the API or not. These “transactional emails” will therefore have to be sent from somewhere else.
Or did I miss something?
04.24.2015
Chris MailChimp
Hey Erwan,
The definition of transactional email is a loose thing at best. With the new API workflow, you now have 100% control over the actions which trigger marketing emails to your customers, much like transactional email services including Mandrill.
If your transactional emails look anything like marketing emails (for instance, offering a promotional code after a purchase), even if they’re technically transactional, you should provide an unsubscribe link for your readers. Mistakes in your unsubscribe process can cost you customers and erode trust, so consider making your transactional unsubscribe process follow the same easy flow as bulk email.
Thanks!
Chris
04.25.2015
Joshua
Hi Chris,
I’m exploring this feature in the playground /automations/{workflow_id}/emails/{workflow_email_id}/queue
and I got the following result. May I know what am I doing wrong?
title: Invalid Resource
status: 400
detail: The resource submitted could not be validated. For field-specific details, see the ‘errors’ array.
instance:
errors:
0:
field:
message: Schema describes object, NULL found instead
Regards,
Joshua
11.10.2015
Chris MailChimp
Hey Joshua,
I’ve only been able to replicate the issue when I POST an empty request body. Can you write into apihelp@mailchimp.com with more details about what your POST request body looks like?
11.10.2015
Steve
Hi,
I’m trying to figure this whole automation thing out. I have one list and have three groups on that list.
Ideally I’d like to be able to trigger three separate automation campaigns when I manually assign a subscriber to one of the groups.
For example:
Group A will receive Group A automated emails, Group B would receive Group B emails and so on.
Is this possible?
02.05.2016
Brandon MailChimp
Hi Steve, that’s definitely something you can do with MailChimp’s Automation features. The exact workflow would vary a bit depending on your specific needs, but you’d essentially just need to create three separate automation campaigns, and set up each with its own unique, group-specific trigger criteria, segment, and sending time. Each of the campaigns could contain as many different emails as needed, and you could adjust the delay between the delivery of each email in the sequence as needed. Our Knowledge Base has a lot of valuable information that will help explain how to use Automation in MailChimp, but if you still some assistance, don’t hesitate to get in touch with our support team directly. They’ll be able to collect more information from you and help walk you through the process.
02.23.2016
Wynn
Hi Chris,
So with the API triggered workflows, will I be able to do the following (trying to mimic what HubSpot and Marketo would be able to do in conjuction with Wistia):
Track Wistia video events such as # of video plays, partial views, complete video completions, etc., tag them accordingly and send them segmented messages based on their behavior.
If so, that would be awesome! I know that I would need to upgrade to a paid plan in order to do that. Can you give me some pointers on how I would go about doing that? Thank you!
04.24.2016
Brandon MailChimp
Hey Wynn, if you still have a few questions regarding API & Automation functionality, would you mind contacting our support team directly? They’ll be happy to assist!
05.18.2016