---
canonical: https://amplience.com/developers/docs/workforce/flows/getting-started/
title: Build a flow in 5 minutes
description: Get started with Workforce Flows in minutes. Learn how to build, configure, and run automated workflows that connect tasks and streamline content processes.
audience: Business User
image: https://cdn.media.amplience.net/i/ampproduct/ve-flows-docs-example2-lm?w=1200&h=630
image_width: 1200
image_height: 630
date_published: 2025-06-25
date_modified: 2026-06-226
how_to:
  name: "Build a flow in 5 minutes"
  description: "How to build, configure, and run an automated Workforce Flow that generates a blog post from a user prompt, including an optional human review step."
  total_time: "PT5M"
  steps:
    - name: "Create the flow"
      text: "From the Workforce Flows page, click Create new flow and give the flow a name and description. The Flow Designer opens ready for you to start designing the flow."
      anchor: "step-1-create-the-flow"
    - name: "Add a trigger"
      text: "In the Actions library, expand Manual Triggers and drag the Chat Trigger action into the editing area. Once added, its configuration panel opens — enter a user prompt such as 'Enter a blog subject'."
      anchor: "step-2-add-a-trigger"
    - name: "Add a content generation action"
      text: "In the Action library, expand the content generation actions and drag the Blog action below the Chat Trigger. Connect the OUT port of the Chat Trigger to the IN port of the Blog action. In the configuration panel, select a model and set the Title field to the Message variable from the chat trigger."
      anchor: "step-3-add-a-content-generation-action"
    - name: "Add an output action"
      text: "In the Action library, expand the Output actions and drag the Chat Output action to your flow. Connect it to the Blog action — the Blog content variable is automatically added as the output message. Save your flow."
      anchor: "step-4-add-an-output-action"
    - name: "Enable the flow"
      text: "To allow the flow to be run by non-admin users, an Admin user must set the flow to Enabled. This displays the Run button and allows other users to run the flow."
      anchor: "step-5-optional-enable-the-flow"
    
---

# Build a flow in 5 minutes (or less)

One of the quickest ways to get started with [Workforce Flows](https://amplience.com/developers/docs/workforce/flows/about-flows/) is to create your own. This guide walks you through a simple flow that creates a blog post from a user prompt and outputs the result.

As a bonus, you’ll also learn how to add a human review step to edit, approve, or reject the content.

![Get started flow overview](https://cdn.media.amplience.net/i/ampproduct/ve-flows-docs-example2-lm?w=1880&fmt=png&)

> **Info: Permissions for building flows**
> To build and manage flows for your organization you will need Administrator permissions. See [Workforce permissions](https://amplience.com/developers/docs/concepts/permissions/roles/#roles-and-workforce).

## Step 1: Create the flow

From the Workforce Flows page, click **Create new flow**, and give the flow a name and description.

![The flows list shows the flows on this hub](https://cdn.media.amplience.net/i/ampproduct/flows-click-to-create-flow?w=1880&fmt=png 'The flows list shows the flows on this hub')

The Flow Designer opens ready for you to start designing the flow.

![The flow designer opens ready for you to start building a flow](https://cdn.media.amplience.net/i/ampproduct/wk-build-flow-step-1-with-disable-mode-v2?w=1880&fmt=png 'The flow designer opens ready for you to start building a flow')

## Step 2: Add a trigger

Every flow starts with a trigger. The trigger defines what causes the flow to run. In this example, we're going to use a **Chat trigger** to start the flow manually.

**To add the trigger:**

1. In the Actions library, expand **Manual Triggers**.

2. Drag the **Chat Trigger** action into the editing area.

Once the trigger is added to the flow, its configuration panel opens ready for a user prompt to be entered.

> **Tip:** In this example we'll be creating a blog, so use something like "Enter a blog subject".

![Add a Chat trigger action to the flow](https://cdn.media.amplience.net/i/ampproduct/wk-build-flow-add-chat-trigger-with-disable-mode-v2?w=1880&fmt=png 'Add a Chat trigger action to the flow')

> **Tip: How flows are triggered**
> In this example, we’re using a manual trigger, but content flows can also be triggered by external events using **webhook triggers**, allowing you to fully automate your processes. Learn more about [Triggers](https://amplience.com/developers/docs/workforce/flows/triggers/)

## Step 3: Add a content generation action

Now that we have the trigger for our flow, we need to add the next action. In this example we'll add a **content generation action**.

> **Tip:** Content generation actions let you use both built in and custom templates that are available elsewhere in Workforce. Learn more about [content generation actions](https://amplience.com/developers/docs/workforce/flows/action-reference/#content-generation-actions).

For this flow, we'll use the [blog action](https://amplience.com/developers/docs/workforce/flows/action-reference/content-generation-actions/#blog).

**To add the blog action:** In the Action library, expand the content generation actions, then drag the Blog action to just below the Chat Trigger.

![Add the blog action to the flow](https://cdn.media.amplience.net/i/ampproduct/wk-build-flow-add-blog-with-disable-mode-v2?w=1880&fmt=png 'Add the blog action to the flow')

You'll see instructions on the right telling you to connect the **IN** port of the **Blog** action to the **OUT** port of another action.

1. Click on the OUT port of the Chat trigger and drag to the IN port of the Blog action.

2. Set the Blog action input values:

   - Select the **Model** in the configuration panel, along with any other information, such as tone of voice and audience. **Tip:** The Blog action must selected to display its configuration panel.

   - Click in the **Title** field. The [Variables](https://amplience.com/developers/docs/workforce/flows/action-reference/#input-field-variables) picker opens for you to choose from the variables output by the chat trigger. Select `Message` to set the title of your blog to the text that will be entered by the user.

![Set up the fields of the blog](https://cdn.media.amplience.net/i/ampproduct/wk-build-flow-connect-blog-with-disable-mode-v2?w=1880&fmt=png 'Set up the fields of the blog')

> **Tip:** Find out more about [ports and input values](https://amplience.com/developers/docs/workforce/flows/action-reference/#inputs-outputs-and-ports).

## Step 4: Add an output action

The final step is to add an output action to output the content generated by the Blog action.

1. In the Action library, expand the **Output** actions, and drag the **Chat Output** to your flow. Connect it with the Blog action. Note that the `Blog content` variable is automatically added as the Chat output message.

2. Save your flow.

![Adding an output action to output the generated blog content](https://cdn.media.amplience.net/i/ampproduct/wk-build-flow-add-output-with-disable-mode-v2?w=1880&fmt=png 'Adding an output action to output the generated blog content')

> **Info:** At this point, if you have Admin permissions you can **Test** the flow.

## Step 5: (Optional) Enable the Flow

To allow the Flow to be run by non-admin users, an Admin user must set the Flow to **Enabled**. This will display the **Run** button and allow other users to run the flow.

![Enabling a flow to be run](https://cdn.media.amplience.net/i/ampproduct/wk-build-flow-enable-flow-v2?w=1880&fmt=png 'Enabling a flow to be run')

Read more about [Enabling Flows to be run](https://amplience.com/developers/docs/workforce/flows/review/#enabling-flows-to-be-run).

## Try it out

The example blog flow is ready to run (see the [Enable the Flow](#enable-the-flow) step above):

1. Click **Run** at the top of the window
2. In the **Start a new run** dialog, enter a label to help find the results in the list of runs later, then start the run.

![The label helps you identify a run of the flow in the runs list](https://cdn.media.amplience.net/i/ampproduct/wk-build-flow-try-it-out-with-disable-mode-v2?w=1880&fmt=png 'The label helps you identify a run of the flow in the runs list')

While the run is in progress, you can click **View flow** to follow progress through the flow. The flow progress is shown in the main window, with the flow displayed to the right. As the flow runs, the current action is highlighted.

![Click view/hide flows to view progress within the flow](https://cdn.media.amplience.net/i/ampproduct/wk-build-blog-flow-in-progress-with-disable-mode-v2?w=1880&fmt=png 'Click view/hide flows to view progress within the flow')

When the flow is complete, the content generated by the blog action is displayed.

![The flow run is complete and the generated content is displayed](https://cdn.media.amplience.net/i/ampproduct/wk-build-flow-complete-with-disable-mode-v2?w=1880&fmt=png 'The flow run is complete and the generated content is displayed')

The completed run is shown in the "Runs" window. You can open the flow again to check the output or to run it again.

![The completed run is shown in the Runs window](https://cdn.media.amplience.net/i/ampproduct/wk-build-flow-runs-list-with-disable-mode-v2?w=1880&fmt=png 'The completed run is shown in the Runs window')

In just 5 steps you've created your first flow. From here, you might want to add another action to translate the content, or use the output as input for another action.

## Bonus step: add human review

In this bonus step you'll add a human review stage to the example flow, giving you the opportunity to approve, reject or edit the generated content.

1. In the Action library, expand the **Review and moderation** actions and drag the **Human review** action to your flow, connecting it with the **Chat output** action.

2. Set inputs for the review action:
   - Set the **Review label** to use the `Message` entered by the user in the chat trigger
   - Add some instructions for the reviewer in the **Review Task Instructions** field
   - Select the `Blog output` as the **Data** to be reviewed.
   - Optionally, adjust the **Review time**, which defines how long the review remains active. The default is 7 days.

![Add the human review action to review the generated blog content](https://cdn.media.amplience.net/i/ampproduct/wk-build-flow-add-review-with-disable-mode-v2?w=1880&fmt=png 'Add the human review action to review the generated blog content')

Now run the flow by clicking **Run** at the top of the window.

When the review step is reached, the flow pauses and waits for you to begin the review process. Click **Open review** to start your review.

![Open the review window](https://cdn.media.amplience.net/i/ampproduct/wk-build-flow-review-paused-with-disable-mode-v2?w=1880&fmt=png 'Open the review window')

Check the content and make any necessary changes, choose whether to approve or reject the content.

![Make any changes you want and choose to accept or reject the content](https://cdn.media.amplience.net/i/ampproduct/wk-build-flow-review-output-with-disable-mode-v2?w=1880&fmt=png 'Make any changes you want and choose to accept or reject the content')

Close the review window when you're finished.

The flow will resume running. In this example the review is the last step and the flow run is complete. It will show whether you accepted or rejected the content.

Notice that there are 3 outputs from the Human review action: accepted, rejected or expired. You can connect different actions to each of these outputs, allowing you to branch the flow according to the result of the review.

![The flow run is now complete and the content is shown as accepted or rejected](https://cdn.media.amplience.net/i/ampproduct/wk-build-flow-review-approved-with-disable-mode-v2?w=1880&fmt=png 'The flow run is now complete and the content is shown as accepted or rejected')

> **Tip: Ways of completing reviews**
> In this example, the review is completed directly from the flow. However, in most cases, you’ll complete reviews from the **Review** list which lets you review the output of flows triggered automatically, such as by webhooks. See [Reviewing flow output](https://amplience.com/developers/docs/workforce/flows/review/).

## Related pages

[Running and reviewing flows](https://amplience.com/developers/docs/workforce/flows/review/)

[Example flows](https://amplience.com/developers/docs/workforce/flows/examples/)