> 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/flows-alarms.md).

# Flows : Alarms

Alarms let you bring events from the world outside FlytBase such as sensors, cameras, fences, fire panels, and other security or monitoring systems, directly into your Operations dashboard. When one of these systems detects something, it sends an **alarm** to FlytBase, where it appears in real time and can automatically launch a drone response through a **Flow**.

Alarms are set up using **Flinks** — FlytBase's connectors for third-party apps and sensors. An **Alarm Flink** groups one or more **alarm sources**, and each source gives you a secure web address (a webhook) that your external system calls to raise an alarm.

### How Alarms Work

1. You create an **Alarm Flink** and add one or more **alarm sources** to it.
2. Each alarm source provides a **Trigger URL** (and an authorization token). You give these to your external system.
3. When the external system detects an event, it sends a small message (a JSON payload) to that URL.
4. The alarm instantly appears on your Operations dashboard, and — if you've connected a **Flow** — it can trigger an automatic or operator-confirmed drone response.

{% hint style="info" %}
Alarms (Flinks) capture and display events; **Flows** decide what happens in response.
{% endhint %}

## Setting up a new Flow with Alarms

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

1. In the Operations dashboard, go to **Flows** and select **Create**.

<figure><img src="/files/wNrpa9Z8iHBa3W04HOve" alt=""><figcaption><p>Navigating to Flows</p></figcaption></figure>

2. Choose **Alarms** from the dialog, then select **Next**.

<figure><img src="/files/cAwFe2ukLv4PqDAnDYMs" alt=""><figcaption><p>Creating a Alarms Flow</p></figcaption></figure>

#### Name

1. Give the Flow a clear, recognizable **name**. Names must be unique, so you can tell your Flows apart at a glance.

#### Trigger — choose the alarm sources

2. Under the **Trigger** drop-down, select the **Alarm sources** to associate with this Flow.

{% hint style="info" %}
You can link multiple Alarm sources to a single Flow if they require a common response action while each Alarm source can only be linked to one Flow to ensure a consistent response.
{% endhint %}

<figure><img src="/files/QOGBpZj5Y6w3yAUTkq7K" alt=""><figcaption><p>Name and Alarm Source(s) selection </p></figcaption></figure>

#### Action — what the drone should do

3. Choose one **action**:

* **Go to alarm location** — the drone flies straight to the coordinates carried in the alarm.
* **Perform mission** — the drone flies a pre-planned mission you select.

**If you choose "Perform mission"**

Select a **mission** for the drone to fly. To keep automated responses safe and predictable, only missions that:

* **end with Return to Home (RTH)**, and
* **belong to the chosen site**

are available to pick. The mission card shows its type, estimated flight time, distance, finish action, and site. The mission flies with the parameters it was planned with.

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

**If you choose "Go to alarm location"**

Set the flight parameters for the response (the drone uses the alarm's coordinates for the destination):

* **Take-off altitude** — height for the initial climb (relative to the take-off point).
* **Task altitude** — the cruise altitude for the transit (shown for supported drones).
* **Waypoint altitude** — the altitude at the destination.
* **Drone speed** — the transit speed (where the drone supports setting it).
* **Finish action** — fixed to **Hover**, so the drone holds over the location on arrival, ready for the operator.
* Each field shows its allowed range to guide you, and values are displayed in your account's preferred units.

<figure><img src="/files/ymRvLzVr2jUtjkk0Hsk2" alt="" width="111"><figcaption><p>Selecting a Device, and setting Go-to Location parameters. </p></figcaption></figure>

#### Response mode — automatic or operator-confirmed

4. Select the **Response Mode**:

* **Manual response**: The Dashboard prompts you to select an action in response to the alarm when it is triggered.
* **Automated response**: The drone automatically executes the selected action without operator intervention when an alarm is triggered.

#### **Associate with a Site**

5. Select a site to filter out the devices that will respond when the alarm is triggered. This scopes the available missions and devices to that location.

#### Device — which drone responds&#x20;

6. Choose the responding **device** (a drone and its dock):

* **Choose when alarm is raised** — the operator picks an available drone at response time (manual responses only).
* **Choose now** — assign a specific drone and dock to the Flow in advance.

{% hint style="warning" %}
Only **one device** can be associated with a Flow. Automated responses always require a device to be chosen in advance.
{% endhint %}

* **Action Go To Location/ Performing Mission:** Depending on the chosen Action, either select a pre-existing mission associated with the site or set parameters for the **Go-to Location** maneuver.
* **Drone speed:** Set the speed at which the drone will travel to the alarm location.

#### Review and save

7. Once all the parameters are set, click on the **Create** button and your alarm flow will show up in **My Flows**.&#x20;

* An **Overview** of the flow can be viewed on the right side of the screen.

<figure><img src="/files/emeS6wPtvWalVyqnMTHz" alt="" width="375"><figcaption></figcaption></figure>

{% hint style="info" %}
Select **Create** to save (or **Update** when editing), or **Discard** to cancel.
{% endhint %}


---

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