# Connecting Workflow Components

After defining your triggers and adding action steps, you need to connect them to define the flow of your automation. You also need to save your work and understand the difference between draft and published states.

## Creating a Flow Sequence

Workflow components (Triggers and ACTIONS blocks) are linked together to create a sequence. Each trigger and "ACTIONS" block has a small **blue dot (●)** at its bottom centre. This is the connection output point. 

<div align="left"><figure><img src="/files/CJA05lpz6zPPGPVyuOke" alt="" width="375"><figcaption></figcaption></figure></div>

## **Sequential Action Blocks:**

\
You can chain multiple "ACTIONS" blocks together to create multi-stage processes, often involving delays and different entry and exit mechanisms.  You can get as creative and complex as you like. Always remember to test in staging before shipping to production. Please see some relevant examples below.&#x20;

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

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


---

# 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://userflux.gitbook.io/userflux-docs/feature-guides/user-journeys/user-flows/connecting-workflow-components.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.