Flows

Flows are FlytBase automations that detect events, such as alarms or flight activity, and trigger a defined response like launching a drone or notifying the team.

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.

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.

Setting up Flows

Accessing the Flows Manager:

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

Flows tab in Navigation Drawer

Flows Section Tabs:

• My Flows: Here you can create, edit, and delete your flows. You can also enable and disable them when required.

• Logs: This tab records the trigger time and status of each flow.

Flows Manager

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.

Currently only Alarms and Notifications based flows are supported.

Selecting Category for Flows

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. Confirm the deletion on the prompt that appears.

Deleting a Flow

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.

Flows Logs

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.

Detailed Flows Log

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.

Alarms and Flows Logs (Sidebar)

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.