> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/documentation/automation/guide/how-to-start.md).
# How to start
To start creating a flow in the Equipme Automation Tool, navigate to the **Workflows** section. This area gives you an overview of all existing flows. When you’re ready to build a new one, click on **Create Flow**. This creates a new, blank flow, which you can access by clicking on its name. Once inside, you’ll be in the **Flow Designer**, the workspace where you’ll design and customize your automation.
Before diving into flow creation, it’s helpful to have a specific use case or business logic in mind. This will make it easier to select the right components and set up a flow that serves a meaningful purpose.
In the Flow Designer, you’ll see a panel on the left side containing **utilities** and **applications**. Here’s a quick breakdown:
* **Utilities** are general tools that help structure and control the flow. They include options like Filters, Converters, Timers, and Tasks. For instance, Filters can guide data based on certain conditions, while Timers add delays between actions to space things out as needed.
* **Applications** are connections to external services, such as email systems, databases, or third-party apps like Airtable or Amazon S3. These applications allow you to integrate your flow with other platforms you use, letting data move seamlessly across systems.
To begin building your flow, select a **component** from the left panel—either a utility or an application—and drag it onto the main canvas. Dropping a component on the canvas adds it to your flow and prompts a setup menu to appear on the right side of the screen. This menu allows you to customize the component’s settings.
Each flow starts with a **trigger**, which is the event that sets the entire process in motion. For example, a trigger could be when a form is filled out or an email is received. After setting the trigger, you add **actions -** the tasks that occur in response to the trigger. For instance, if the trigger is a form submission, an action might be sending a confirmation email or routing the information to the appropriate team.
You can add as many components as needed, allowing you to build a flow as simple or complex as your use case requires. Each component can be connected to others, creating a sequence of actions and conditions that guide the flow based on specific data or criteria.
Once you’re satisfied with the setup, make sure to click the **Start Flow** button at the top of the screen. This activates the flow, making it live and ready to respond whenever the trigger event occurs. If you don’t press Start Flow, the automation will remain inactive, saved but not running.
With this setup, you can create sophisticated, automated processes that handle tasks efficiently and without constant supervision. The drag-and-drop interface and customizable options make it easy to design flows that perfectly fit your needs.
---
# 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:
```
GET https://hub.equipme.io/documentation/automation/guide/how-to-start.md?ask=
```
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.