### This lesson contains two videos (30mns and 10mns). Always advocate for yourself, your energy, and your learning style. It's a non-negotiable part of learning. If you need breaks, take 'em.

A workflow is a templated set of actions that can be triggered when a user is added to a specific segment. You can set conditions that allow you to: * automate onboarding or welcome emails * send different emails based on the segments a user is in * resend an email if not opened in a certain period * build an automated sales email workflow * do other cool stuff based on the users actions (and not your assumptions about them! data!!! 🥳) > The benefit of a workflow is to "set it and forget it." It eliminates unnecessary repeat work and lets you focus on what's most important in your business. Workflows use basic logic, which means you can speak them out loud and they make total sense. This is a *huge* help when you're building your own over the next couple of days. If you ever get overwhelmed, just remember to speak to yourself linearly, moving step by step. Let's take a look at the basic structure here. We begin with a trigger. Flodesk's only trigger is when a user is added to a segment. From the main workflow screen, you can also add one user at a time to a workflow. That's useful if you ever maybe want to add a friend to an offering without having to send them the form or if you're working with something like Zapier or any other automation software. Because workflows are linear, note that your workflow (once it's published) is effective immediately. So if you then go and add someone to your workflow, it'll start executing.

### In the same way you can add someone to a workflow, you can remove a specific subscriber from one. It's one at a time so there really shouldn't be much reason to do it. Maybe if you find an issue after someone has signed up, you can know that this is there without completely firebombing the whole thing.

### Workflows use basic logic If this, then that. This is why I'm all about mapping them ***before*** you try to start building. We do this in programming, too. Many devs write pseudo-code, which is a placeholder to get your thoughts straight before you start thinking about writing working code. It's a *lot* easier to reason about a problem when you're just thinking about what you need to accomplish and not about doing things in the best way. To help us understand all of the features we have available here, let's step through our options when creating a workflow

### Analytics for workflows + Editing workflows Flodesk has good analytics for workflows. Just like regular emails, you can look at who's in the workflow, where they are, who has opened one, etc.

### Action Items You've got enough stuff to worry about 🤷🏽‍♀️ * Do something nice for yourself. Eat the thing you've been craving and putting off. * You could use an energy cleanse, bb. Hop in a nice salt bath, (safely) preen under the sun, and/or wash your hair. And I mean really get into that scalp and get the energetic gunk out (I *love* a teensy bit of sea salt sprinkled on my crown before washing, ymmv obvs.)

Lesson 3 - Understanding Flodesk Workflows