> For the complete documentation index, see [llms.txt](https://docs.flytbase.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flytbase.com/flinks-and-flows/flows.md).

# Flows

**Flows** in FlytBase is a dynamic feature designed to streamline operational efficiency by configuring the drone's response to specific alarm triggers or operational notifications. These workflows allow for the deployment of drones in response to various alarm sources, with the option for missions to be approved manually or carried out automatically for repetitive events. They also allow selected organisation members to keep track of the drone operations by staying notified through emails or SMS. 

This capability empowers the integrated **Flinks** and significantly enhances responsiveness in sectors such as emergency response, security, and infrastructure monitoring, by reducing response times and the need for constant human intervention. 

### Types of Flow

When you create a Flow, you choose what kind it is:

| Flow type                     | What it does                                                                                                   |
| ----------------------------- | -------------------------------------------------------------------------------------------------------------- |
| **Alarms**                    | Responds to a raised alarm by launching a drone, either to the alarm's location or by flying a chosen mission. |
| **Operational notifications** | Sends a notification (by email) when a flight event occurs.                                                    |

{% hint style="info" %}
Alarm Flows depend on **alarm sources**, which you set up first as **Flinks**. See the companion **Alarms** guide for creating an alarm source and its trigger URL.
{% endhint %}

## Setting up Flows

**Accessing the Flows Manager:**

* Select **Flows** from the Navigation Drawer to open the **Flows** section.

<figure><img src="/files/L86JeYI9sMDGdHMPn7zw" alt=""><figcaption><p>Flows tab in Navigation Drawer</p></figcaption></figure>

**Flows Section Tabs:**

* **My Flows**: Here you can create, edit, and delete your flows. You can also enable and disable them when required.
* &#x20;**Logs**: This tab records the trigger time and status of each flow.

<figure><img src="/files/pvwpymbruX3AXmXIDhvK" alt=""><figcaption><p>Flows Manager</p></figcaption></figure>

## Creating a new Flow

To create a new Flow, please follow the following steps:

* In the **My Automations** tab, click on the **Create** button.
* A dialog box will appear, prompting you to select a category.&#x20;

{% hint style="info" %}
Currently only Alarms and Notifications based flows are supported.
{% endhint %}

<figure><img src="/files/xoTjlD1hD2tLTMyPSYoT" alt=""><figcaption><p>Selecting Category for Flows</p></figcaption></figure>

**Editing and Deleting Flows:**

* To **edit** any Flow, click on it and modify the necessary parameters.
* To **delete** a Flow, tick the checkbox next to the flow and click on![](/files/B5mSy7PFIpR3a1YdGTfI). Confirm the deletion on the prompt that appears.

<figure><img src="/files/5asLmHbkEdZYjovaM2Js" alt=""><figcaption><p>Deleting a Flow</p></figcaption></figure>

## Flows Logs

Flows logs provide a comprehensive record of automation activities, including:

* **Alarm /Operational Notification Identification**: Identifies which alarm, flight event or operational event initiated the automation routine.
* **Time**: Notes the time at which the Flow was activated.
* **Status**: Shows whether the Flow response was successful or not.

<figure><img src="/files/C4Sd3rnzQN20UOVUlZ4S" alt=""><figcaption><p>Flows Logs </p></figcaption></figure>

**Detailed Log View:**

* Clicking on a log entry opens a detailed view, where you can see:
  * The alarm received and its status.
  * The action taken in response to the alarm and its status.
  * The response mode and the device that responded.
* **Additional Options:**
  * **Rerun Flow**: Allows you to execute the flow again again if required.
  * **Flight Logs**: Access logs from the flight conducted in response to the alarm.
  * On the right, a map is displayed, centered on the alarm's location.

<figure><img src="/files/Xl0Yuy7rcBkpxNmyG0bh" alt=""><figcaption><p>Detailed Flows Log</p></figcaption></figure>

{% hint style="info" %}
**Quick Alarm and Flows Logs:**

A **condensed version** of the Alarms and Flows logs can be found in the **Integrations Panel** on the right side of the Dashboard. This panel also displays all Flinks, any alarms triggered within those Flinks. Additionally if a flow is configured with an alarm you can see the response details as well.&#x20;
{% endhint %}

<figure><img src="/files/jMXYRdioGSAEzMNsOWiu" alt=""><figcaption><p>Alarms and Flows Logs (Sidebar)</p></figcaption></figure>

### Use Cases

* **Automated security response:** Link a perimeter alarm source to an **Automated** alarm Flow so a drone launches to the breach location the instant an alarm is raised — no operator needed.
* **Operator-in-the-loop dispatch:** For sensitive sites, use a **Manual** alarm Flow so a human confirms every launch with **Send drone**.
* **Scripted incident routes:** Use **Perform mission** with a pre-planned RTH mission when you want the drone to fly a known, repeatable inspection path in response to an event.
* **Keeping stakeholders informed:** Use a notification Flow to email the right people automatically whenever a key flight event — like a thermal alert or an object detection — occurs.


---

# 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://docs.flytbase.com/flinks-and-flows/flows.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.