Workflow Show & Tell - Share and win!

Hey Everyone! I wanted to share a way that we have our workflow's communicate with each other using lists. This is so far just the blueprint so I'm using delay nodes in place for action nodes (the reason is because I didn't want campaigns to be created from the workflow yet). So in the workflow, I have a filter that checks if the user engaged with a specific email; if they did, we want to send them into a nurture workflow and if not, they'll continue down the "No" column for the rest of the main workflow. So if they do engage with that email, we enroll them into our nurture workflow, which in this case lasts 3 days. In that nurture workflow, we add the user to a list and at the end, we remove them from that same list. Back to the main workflow (the image), we delay the user for 3 days because that's how long they'll be in the nurture for. At the end of the 3 days, we check if they're still in the list aka the nurture workflow. If they're no longer in that workflow, we let them continue down our main workflow.

Hello Everyone! I wanted to share with you all how my team has utilized workflows to completely automate our daily marketing app push programs. Initially, we had used recurring messages to serve our daily marketing pushes. But we quickly learned that this had it's limitations. Turning off a recurring message is bulky and time consuming, and then turning back on is just as cumbersome. We wanted to have a way to turn off our pushes for exclusive events or test easily within our messages. How we accomplish this is by triggering the workflow off a scheduled recurring list. For this example it is our Push1and3 list where we target users with positive and loyal brand affinities that have been actively engaged with push in the last 9 days. We run this workflow daily at 3:30pm to see if users qualify. After we do some other segmenting filters via Fields Match, we use the A/B Split filter to divide users among the messages we've created as App Pushes. We've found through personal testing that users are unlikely to be thrown into the same splits daily and message variety has not become an issue. We can now easily: turn off an entire workflow for special ad hoc events and test and replace poorly performing messages.

When a user comes into our system they're assigned a category associated with where they signed up for our emails. So if they were researching auto warranties on our site, their profile has the category of "auto warranty." But as they become a lead for different categories, the category on their profile changes. So to make sure we know which users came through each category if they were associated with multiple ones, this workflow simply adds them to a static list for each category so we'll always have a list of auto warranty users even if some of those people went through our site and also bought a medical alert device or a walk in tub later on. I think this is a pretty cool use case for workflows beyond sending emails to users and it solves a problem we were having in a simple way.

Hello again! I already shared the pregnancy workflow on the User Group, so I'll show you something different here. This is our primary workflow that we use to send new contacts down the right path when they enter our system. Our engineering team kinda has a lot of people lumped into one list, and rather than ask them to do the backend work to separate them a bit, it was easier for me to just create this automation. Contacts are added to this workflow when added to our Marketing Subscribers list. After a brief delay, we reach our first decision point. It looks at the 'source' field to see if the contact originated from one of the 7 newsletter signup sources, and if so, sends them to the newsletter welcome list, which triggers a separate workflow. The next decision point is looking to see if the subscriber has a value in the "brand_ids" field, which is values stored in an array. If so, this indicates that the subscriber requested information on one of the thousands of brands we represent, and we need to send them through the lead nurture flow, which is a confirmation email followed by several follow-ups. The next decision point is the exact same as the previous, except the data is relayed to us in a different fashion—a singular value on the "brand_id" field, not stored in an array. Since we utilize the catalog feature, the way we look up the value is different, and therefore it needs to be a separate set of emails coded a little differently. Otherwise, it's the same. If someone reaches the next decision point, it means they were not a newsletter subscriber and did not request brand information, but instead simply should receive generalized category information. This triggers a separate email campaign. Lastly, anyone leftover is put into a holding pattern (for my own purposes of troubleshooting and spot-checking) and then added to a list called "Didnt Work". Ideally, no one should be added to this list, but inevitably many are. There are many instances where a contact was submitted in an unusual fashion that did not meet any of the preexisting criteria. At the very bottom you will see that the two lead nurture flows end with a dedicated NPS survey. We send it to them if they did not click an NPS link in one of the previous emails. The last decision point looks to see if the subscriber interacted with anything, and if so, adds them to a special list of engaged users. They will be added to our normal newsletter cadence. If not, it is likely we will simply not email them again. That's basically it! The rest is pretty straightforward.

Hi All! Here is our remove test accounts work flow. It looks through all emails in our system to remove internal test emails (anything ending with @consumeraffairs and a plus sign or test) to make sure they aren't bulked in with our normal sends, hence messing with our numbers.

Hi, Here is the flow that we used for our IP Warm UP, we decided to complete the whole warm-up using one campaign in which each customer just flowed in once. Users were added to a standard list that would flow them into the workflow, once they received the campaign they would be taken out of the list.