# Workflow Editor Actions Panel

When editing a user flow, an "Actions" panel or toolbar provides quick access to various components and settings for building and managing your workflow.

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

This panel typically includes the following options:

**Add Trigger:**

* **Icon:** Lightning bolt
* **Description:** Allows you to set up or modify the initial condition(s) that will start the workflow. This defines how users enter the flow.
* **Use Case:** Defining if a flow starts based on a user action, a profile update, a schedule, or an API call. [See the adding triggers page for a more detailed break down. ](/userflux-docs/feature-guides/user-journeys/user-flows/adding-a-trigger.md)

**Add Step:**

* **Icon:** Stacked items / Drawer (looks like a filing cabinet drawer)
* **Description:** Enables you to introduce a new action or stage within the workflow. Steps are the individual tasks or processes the workflow executes after a trigger.
* **Use Case:** Adding actions like sending an email, updating a user profile, adding a delay, or tracking user events..

<figure><img src="/files/3ozv1Sp6JT1MQfmPzPLz" alt=""><figcaption></figcaption></figure>

**Add AB Split:**

* **Icon:** Flask / Beaker&#x20;
* **Description:** Allows you to divide users into different paths within the flow to test variations of a message, timing, or action (A/B testing).
* **Use Case:** Testing two different email subject lines to see which gets a higher open rate, or sending different offers to segments of users.

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

**Entry Criteria:**&#x20;

* **Icon:** Entry arrow&#x20;
* **Description:** Controls how often users can re-enter this specific workflow. This helps prevent users from being spammed or experiencing the same flow repeatedly in a short period.
* **Use Case:** Setting rules like "a user can only enter this welcome flow once" or "a user can re-enter this cart abandonment flow after 7 days if they abandon another cart."

<figure><img src="/files/05KBdj40FQrUuEtpM0nw" alt=""><figcaption></figcaption></figure>

**Exit Criteria:**

* **Icon:** Exit arrow&#x20;
* **Description:** Defines the conditions under which users should be removed from the workflow, even if they haven't completed all the steps.
* **Use Case:** Removing a user from an onboarding flow if they complete a key activation event, or removing them from a promotional flow if they make a purchase.

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

Note that when you apply an entry / exit criteria through the actions panel it will apply to the whole workflow.&#x20;

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

This is a critical distinction as you can also apply entry condition at a step level as well.

\
![](/files/6GjsUW8OxsbUb7hi1u9I)

To see how this works in practice proceed to the next page on adding steps.


---

# 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/workflow-editor-actions-panel.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.
