> For the complete documentation index, see [llms.txt](https://docs.getgymini.com/gymini/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getgymini.com/gymini/features/features-overview/workflows/workflow-steps/utilizing-the-if-else-step-in-gyminis-workflow-builder.md).

# Utilizing the If-Else Step in Gymini's Workflow Builder

**Introduction**

The If-Else step in Gymini's Workflow Builder is a dynamic tool that allows you to create divergent paths in your workflow based on various conditions. This guide will explore how to effectively use the If-Else step to build sophisticated workflows that can cater to different scenarios.

**Please Note When using Includes/ Does Not Include as a condition:** 

<pre data-overflow="wrap"><code><strong>There are several conditional parameters in Workflow Builder where you'll have the option to specify "Includes" or "Does not include" such as Tags and other multiple-option custom fields (checkbox fields, dropdown pickers, etc.)
</strong></code></pre>

**Understanding the If-Else Step**

The If-Else step facilitates the creation of conditional paths in your workflow, where different actions are executed based on whether certain conditions are met. Here are some conditions you can base your If-Else steps on:

* Checking if a contact has a specific tag
* The current month
* Whether a contact replied to a message from the workflow
* The specific workflow trigger that initiated the workflow

**Practical Applications of the If-Else Step**

**Example 1: Redeeming an Offer**

In a workflow initiated when a contact clicks a "Redeem Offer" trigger link:

* **Yes Path**: If the contact has an "Offer Pending" tag, this path removes the tag, replaces it with an "Offer Redeemed" tag, and sends an email confirming the successful redemption.
* **No Path**: If the contact lacks the "Offer Pending" tag, this path sends an email informing them that the offer has already been redeemed.

**Example 2: Post-Appointment Feedback**

In a workflow that sends an email to a dentist asking for feedback on an appointment:

* **Trigger Links**: The email contains trigger links representing different outcomes: "Showed and Bought," "No Show," and "Showed but Didn't Buy."
* **Identifying the Clicked Link**: Utilize a series of If-Else steps to identify which link was clicked and direct the workflow accordingly. For instance:
  * **No Show**: Leads to a workflow encouraging the contact to reschedule.
  * **Showed but Didn't Buy**: Leads to a different set of actions.

**Advanced Utilization of the If-Else Step**

* **Time-Based Elements**: Create branches based on time elements such as the current day of the week, specific dates, the current month, year, or even time of day.
* **Ongoing Enhancements**: The Gymini team continually adds more conditional options to the If-Else step, enhancing its versatility and power.

**Conclusion**

The If-Else step in Gymini's Workflow Builder is a potent tool that enables you to build a single workflow capable of executing numerous objectives based on varying conditions. By understanding and utilizing this feature, you can create more responsive and adaptive workflows to meet your marketing objectives.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.getgymini.com/gymini/features/features-overview/workflows/workflow-steps/utilizing-the-if-else-step-in-gyminis-workflow-builder.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.