# Create workflow

Let’s create a simple workflow, that generates Google Ads for our products. It will require only a brief product description as input.

Give a try to this interactive demo:

{% @arcade/embed flowId="FvDdAwCjLULlOAUqWQnd" url="<https://app.arcade.software/share/FvDdAwCjLULlOAUqWQnd>" %}

To start creating a new workflow, proceed to the <mark style="background-color:blue;">**“Workflows”**</mark> menu item and click the <mark style="background-color:blue;">**“New Workflow”**</mark> button in the top right.

<figure><img src="/files/PTLcRhsfWx1Vp59VOLNz" alt=""><figcaption></figcaption></figure>

## Step 1: Edit General Settings

The first thing to do is to configure is general settings of the newly created workflow.

![](/files/0Zp1iABYZbk8a8OZbE1H)

### **Workflow Name**

Your workflow will be displayed under this name:

* in the list of workflows
* as a workflow title for other users
* in the 3rd party integrations

{% hint style="info" %}
This name should be: descriptive, brief, and unique.&#x20;

It answers the question: ***“What does this workflow do?”***
{% endhint %}

###

### **Workflow Status**

Statuses define the access and execution rights for the workflow.

There are two statuses:

**A. Draft**

The default state for any newly created workflow. It means that:

* Only owners can see it
* Only owners can use it
* It’s unavailable via API and 3rd party integrations
* It can be deleted

{% hint style="info" %}
It’s highly recommended to keep your workflow in the **“Draft”** state until you completed building and tested it.
{% endhint %}

**B. Published**

When the workflow is built you change its status to *“Published”*.

It means that:

* Everyone can see it
* Everyone can use it
* It’s available via API and 3rd party integrations
* It can’t be deleted until its status is changed back to *“Draft”* again.

###

### **Workflow Description**

The description provides additional info for users about the purpose of the workflow to set proper expectations.

{% hint style="info" %}
Keep it short yet concise.&#x20;

Answer the next questions: *“What does it do?”* and *“What I need to get started”*?
{% endhint %}

Don’t worry about its length limitations - you’ll be able to provide more details while setting up the input.

###

### **Workflow Icon**

It’s just a visual representation of your workflow in the list of workflows or in the left bar (if the workflow is “favorite”).

{% hint style="info" %}
Make it unique and relevant to the purpose of the workflow.&#x20;

Ideally, all the icons for your workflows should be consistent.
{% endhint %}

Everything could be edited later.

Click <mark style="background-color:blue;">**“Start Creating”**</mark> to build workflow.

## Step 2: Add input

Let’s start building the workflow.

Each workflow starts with the “Input”.

It defines:

1. Properties of the data necessary for the workflow to get started.
2. How the input form looks like for the end users.

Follow the next steps.

### 2.1 Add input block/task.

To add it to the working area drag-drop it from the right toolbar:

<figure><img src="/files/keV0M5lbIMsO0qfjbgGE" alt=""><figcaption><p>Adding input to the workflow builder</p></figcaption></figure>

### 2.2 Edit input settings

To do that, click the <mark style="background-color:blue;">**“Edit”**</mark> icon on the block in the working area.

<figure><img src="/files/tApn3mr91mv0RWpKQMYI" alt=""><figcaption></figcaption></figure>

Settings consist of the next fields:

**Task name**

Define how your input block is named in the workflow builder.

Leave it as is.

**Field label**

Define the title of the workflow’s input in the Input step.

**Input description**

Provide details for end users about the way to input data. You can use [markdown](https://www.markdownguide.org/basic-syntax) there.

**Form layout (deprecated)**

Do nothing there.

**Design Form**

Add one text (string) variable and name it **“Product Description”.**

Let’s configure the actions of the workflow.

## Step 3: Add actions

Google Ads consists of two parts: Headline and Body.

As we already have AI models to generate them in the inventory, just add them to the workflow.

### 3.1 Find actions

To find them out, use the search bar on the right.

![](/files/jKm52nJqjabu9ZdmECNl)

### 3.2 Add actions

Add them to the workflow by drag-n-dropping them into the working area:

<figure><img src="/files/PvR2ODtQ78nUQiSVolsq" alt=""><figcaption><p>Blocks to connect to make Google Ads generator work</p></figcaption></figure>

They won’t work until:

**a) they’re connected**

**b) they have proper input.**

{% hint style="warning" %}
Currently, all the actions are executed in a strict order.&#x20;

**Don’t try to make actions work in parallel** - actions configured earlier will be broken.&#x20;

Every action must be connected to others.
{% endhint %}

### 3.3 Connect actions

For actions to start working, connect them by connecting the dots.

Hover the output of the previous action or input, and drag the connection to the input dot of the next action.

<figure><img src="/files/b6FztJCU21iqyYMCNc76" alt=""><figcaption><p>Connecting blocks to make workflow work</p></figcaption></figure>

Ensure they’re connected before proceeding.

### 3.4 Configure actions

To make the action work, choose the required input data point from the previous input blocks or actions.

{% hint style="info" %}
By default, action blocks have output data points suggested, but **have Empty input data points.**
{% endhint %}

<figure><img src="/files/D4qxqxwe5ZuNglzvKOIw" alt=""><figcaption><p>Configuring action block</p></figcaption></figure>

Let's configure the action block:

**3.4.1 Open the settings of the action block**

**3.4.2 Choose&#x20;**<mark style="background-color:blue;">**“Product Description”**</mark>**&#x20;as an input for both modules**

It’s the one we set as the input of the whole workflow.

**3.4.3 Rename output data points to be more understandable.**

Let’s use *<mark style="color:blue;">“GA Headline”</mark>* and *<mark style="color:blue;">“GA Body”</mark>* for outputs of Google Ads Headline and Google Ads Body modules respectively.

When every action is set properly, the green labe*l “action”* appears in the top right corner of the block.

![](/files/TLns8IuXKVRA3f1vMviX)

Let’s test how this workflow works.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.drafter.ai/build/create-workflow.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.