# Adding a Step

Once your trigger is defined, the next stage is to add steps, which are the actions your workflow will perform.&#x20;

#### Configuring Step Container Entry Conditions (Delay and Filters)

You can define conditions for when and for whom the entire action should run.

Click on the header of the block (the area displaying "No delay No filters"). This will open a dropdown menu.&#x20;

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

Select **"Entry Conditions"** from the dropdown menu. The **"Entry Conditions" modal** will appear, allowing you to set delays and audience filters for this step container.

An entry delay adds a waiting period before users proceed to the actions within this step.

1. In the "Entry Conditions" modal, locate the **"Entry delay"** section.
2. **Toggle the switch** to the right of "Entry delay" to enable it. The switch will turn green.
3. **Enter a numerical value** in the input field (e.g., "20").
4. Select the **time unit** (e.g., minutes, hours, days) from the dropdown next to the input field.

<figure><img src="/files/0xVKKrZk63wPPmtglo2M" alt=""><figcaption></figcaption></figure>

Audience filters restrict which users will proceed through this step based on their profile attributes or segment membership. In the "Entry Conditions" modal, find the **"Audience filters"** section. Click the **"+ Add rule"** button. A pop-up will ask you to choose the type of rule:

* **New Profile Rule:** Filters based on specific attributes of a user's profile.
* **New Segment Rule:** Filters based on whether a user belongs to a predefined segment.

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

**To add a Profile Rule:**

* Select **"New Profile Rule"**.
* A new rule row will appear.
* Click the first dropdown to select a **"user attribute"** (e.g., "companyId", "email").
* Select an **operator** from the second dropdown (e.g., "Equals", "Contains").
* Enter the **"text value"** to match in the third field.

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

**To add a Segment Rule:**

* Click **"+ Add rule"** again if needed.
* Select **"New Segment Rule"**.
* A new rule row will appear.
* Select a **"Segment"** from the first dropdown.
* Select an **operator** (e.g., "Includes", "Excludes").
* Select the specific **segment value** from the third dropdown (e.g., "staff").

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

**Combining Multiple Rules:**

* If you add more than one rule, an **"AND" / "OR"** toggle will appear between them. Click it to define the logic:
  * **AND:** All conditions must be true.
  * **OR:** At least one of the conditions must be true.

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

*(Optional)* You can click the **"Calculate"** link next to "Want to know how many users you're targeting?" to estimate the audience size for your defined filters.

**Saving Entry Conditions**

Once you have configured the delay and filters, click the **"Done"** button at the bottom of the "Entry Con

The header of the "ACTIONS" block on the canvas will update to summarize the configured conditions (e.g., "Wait 20 minutes For filtered audience").

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

Now that the step container is set up, you can add one or more specific actions that will be executed for users who meet the entry conditions.


---

# 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/adding-a-step.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.
