# Publishing a Flow ### About this export | Field | Value | | --- | --- | | **content_type** | lesson | | **platform** | contentstack-academy | | **source_url** | https://www.contentstack.com/academy/courses/data-insights-automating-journeys-with-flows/data-insights-course-5--publishing-a-flow | | **course_slug** | data-insights-automating-journeys-with-flows | | **lesson_slug** | data-insights-course-5--publishing-a-flow | | **markdown_file_url** | /academy/md/courses/data-insights-automating-journeys-with-flows/data-insights-course-5--publishing-a-flow.md | | **generated_at** | 2026-06-08T14:32:02.458Z | > Part of **[Automating Journeys with Flows](https://www.contentstack.com/academy/courses/data-insights-automating-journeys-with-flows)** on Contentstack Academy. **Academy MD v3** — structured for retrieval; no quiz or assessment keys. #### Video details #### At a glance - **Title:** 42-data-insights-flow-publishing - **Duration:** 3m 11s - **Media link:** https://cdn.jwplayer.com/previews/s7HwhRQ0 - **Publish date (unix):** 1752897212 #### Streaming renditions - application/vnd.apple.mpegurl - audio/mp4 · AAC Audio · 114010 kbps - video/mp4 · 180p · 180p · 139308 kbps - video/mp4 · 270p · 270p · 154973 kbps - video/mp4 · 360p · 360p · 163200 kbps - video/mp4 · 406p · 406p · 172260 kbps - video/mp4 · 540p · 540p · 195739 kbps - video/mp4 · 720p · 720p · 232708 kbps - video/mp4 · 1080p · 1080p · 321582 kbps #### Timed text tracks (delivery) - **thumbnails:** `https://cdn.jwplayer.com/strips/s7HwhRQ0-120.vtt` #### Video transcript When, though, I am ready to publish my flow and activate my works or my jobs, there's a couple of different steps. It all starts in this top right corner, actually doubling back to the exports real quick just to not skip any details. You can edit the export configuration with the button in the top right, and then there's a details view that just shows the configuration for that particular job or export that you've configured. Other than that, everything should be pretty consistent throughout the UI. So yeah, so the next step is to ultimately, let's say this flow is perfect, I want to publish it and get it in front of some people. I'm going to go to the top right, which again is our action menu. The only action that I have access to is publish, so I'm going to hit publish. It's going to come through and then do a validation essentially on the flow to tell me things that I need to fix, things that need to be activated. Just for demonstration's sake, if I go in here, for instance, and add a wait condition that isn't configured yet, and then I go to publish, it's going to call out and give you some detail on what things need to be resolved. So in this case, wait and personalize, please provide a valid delay value or condition. As soon as I resolve that, this option goes away. So we'll just delete this real quick, and if I go back to publish now, so the only thing it's prompting me to do is, well, before we publish, we need to activate our jobs. So this is the thing that transitions from the draft state that is net new to an actual runnable state. When we activate it, it's not going to get users pushed to it yet until the flow actually goes live, but it's an interim step to make sure that all of the jobs that you have configured activate. There's not authorization issues, all the things that can come up. So in most cases, that's as simple as just hitting activate. It's going to go through, turn it on. You'll see that the status automatically upgraded to started. So now this job exists in Linux. This is a thing that can run. This is a thing that can accept users and push them downstream to whatever channel and configuration meets those needs. And now also in the top right corner, you'll see that there's no additional sort of configuration validation things to revisit. You did it. You're ready to publish. And publishing the flow to turn it to a running state is as simple as hitting publish. Your bar will turn green at the top to represent the state. The state turns into running. You'll get some confetti to celebrate. And now at this point, if a new email address gets entered, they'll automatically run through this flow or whatever the trigger audience is that you configured. They'll go through the weights, they'll wait for the conditions, and this flow is now totally and completely live. If we go back to the list view, you'll see it show up. So this is our demo walkthrough. So that's kind of all of the steps to creating your first flow end-to-end and all the different various configuration options. #### Key takeaways - Connect **Publishing a Flow** back to your stack configuration before moving to the next module. - Capture one concrete artifact (screenshot, Postman call, or code snippet) that proves the step works in your environment. - Re-read the delivery versus management boundary for anything you changed in the entry model. ## Supplement for indexing ### Content summary Publishing a Flow. Publishing a Flow in Automating Journeys with Flows (data-insights-automating-journeys-with-flows). ### Retrieval tags - Publishing - Flow - data-insights-automating-journeys-with-flows - lesson 09 - Publishing a Flow - data-insights-automating-journeys-with-flows lesson ### Indexing notes Index this lesson as a primary chunk tagged with lesson_id "09" and topics: [Publishing, Flow]. Parent course slug: data-insights-automating-journeys-with-flows. Use asset_references URLs as thumbnail hints in search results when present. Never surface LMS quiz content or assessment answers from this file. ### Asset references | Label | URL | | --- | --- | | Video thumbnail: Publishing a Flow | `https://cdn.jwplayer.com/v2/media/s7HwhRQ0/poster.jpg?width=720` | ### External links | Label | URL | | --- | --- | | Contentstack Academy home | `https://www.contentstack.com/academy/` | | Training instance setup | `https://www.contentstack.com/academy/training-instance` | | Academy playground (GitHub) | `https://github.com/contentstack/contentstack-academy-playground` | | Contentstack documentation | `https://www.contentstack.com/docs/` |