Quick answer: Dock as First Responder means a camera, dispatch, or SCADA alert launches a drone by itself instead of waiting for a pilot. With a DJI Dock 3 ($15,890) and DJI FlightHub 2 auto dispatch, your existing system sends one HTTP POST carrying three credentials and a set of coordinates, and the aircraft is airborne in under 15 seconds. No middleware is required. The whole configuration comes down to two IDs, one token, and one parameter that most people set wrong the first time.
Updated August 2026.
DJI Enterprise has published a full walkthrough of Dock as First Responder in FlightHub 2, presented by Ferdinand Ma. It is the rare product video that is actually a configuration tutorial: it goes into the project settings, the workflow creation, the token generation, the exact HTTP headers and JSON body, and the event rule on the video management system side. If you are trying to work out whether a DFR program is a software project or a weekend, this is the video that answers it.
Below is the workflow broken into the order you would actually perform it, plus the one setting that decides whether your alert launches a drone or just files a notification.
The conceptWhat is Dock as First Responder (DFR)?
Dock as First Responder means using a drone in a box, such as the DJI Dock 3, to put an aerial view over an incident the moment it happens, rather than after somebody decides to fly. FlightHub 2 is the operational brain of the setup. It ties the command center, the video management system, patrol teams, ground vehicles, and the docks themselves into one network.
The distinction that matters is the trigger. In a traditional DFR program, a pilot receives an alert, moves between several software interfaces, finds the location, and starts a flight. With auto dispatch, the third-party system pushes the coordinates and a priority level to FlightHub 2, and the aircraft flies out on its own. Depending on how you configure the alert level, an operator either confirms the alert or is removed from the loop entirely.
This is the piece that separates a docked drone from a DFR program. Hardware alone gives you a drone that can fly a schedule. The integration is what gives you a drone that answers alarms. If you are still deciding on the hardware layer, our DJI Dock 3 review and drone-in-a-box guide covers the dock itself in detail.
The problemWhy automate dispatch instead of just calling a pilot?
DJI makes three arguments in the video, and all three are operational rather than technical.
Lost minutes
When an alarm triggers, time disappears while a pilot mobilizes and manually navigates to the location. Those are the minutes in which the incident is still developing and an aerial view is worth the most.
Blind response
Without pre-arrival aerial assessment, teams deploy into potentially hazardous areas with no picture of what they are walking into. The drone arriving first is the entire point of DFR.
Alert fatigue
False alarm rates in traditional security systems often exceed 90 percent. Manual verification of that volume burns out staff. Automation filters the noise by verifying visually, instantly, without a human deciding whether this one is worth the trip.
The 90 percent false alarm figure is the one to put in front of a budget holder. It reframes the drone from a response asset to a verification asset, and verification is a cost line that already exists in every security operation.
Step oneWhat three credentials does your VMS or CAD system need?
To make an external system talk to a dock, FlightHub 2 needs two answers: which project this belongs to, and which task to run. That produces three items you collect before writing a single line of integration.
| Credential | Where you get it | What it does |
|---|---|---|
| Project UUID | Project settings in FlightHub 2 | The unique ID card for your site. Tells FlightHub 2 which project the alert belongs to. |
| Workflow UUID | Generated when you create an auto dispatch | The target action. Tells FlightHub 2 which specific task to run when the alert lands. |
| X user token | User settings in FlightHub 2 | The authentication key. Without it the request is refused. |
Create the auto dispatch first, because the workflow UUID does not exist until you do. Those three values are everything your VMS, CAD, or SCADA platform needs to hold.
Step twoWhat does the webhook request actually look like?
Integration happens over a standard HTTP POST, or webhook, to the FlightHub 2 endpoint. DJI is explicit that no complex middleware is involved. Two things to get right before you look at the body:
- The domain URL varies by region. Global and EU servers use different endpoints, so confirm which one your account sits on before you paste anything into the address field.
- Three headers are mandatory. Content type set to application JSON, X user token for authentication, and X project UUID for project identity.
In the body, you pass JSON parameters: the workflow UUID, a trigger type, an alert level, and a params object holding latitude and longitude. The coordinates must be in WGS84 format. That is what tells the drone where to look.
The setting worth stealingWhich parameter decides whether the drone actually launches?
Set the level parameter to 4. That value is what authorizes auto dispatch. If the level is not set correctly, DJI warns that the system may only create an alert without ever launching the drone. Everything else in the request can be perfect, the token valid, the coordinates exact, the workflow live, and you will still end up with a notification in FlightHub 2 and an aircraft sitting inside a closed dock.
This is the detail that no spec sheet carries and the one most likely to cost you an afternoon of debugging. It also fails quietly: a wrongly leveled request does not throw an obvious error, it succeeds at doing something less than you wanted. When you run your first end-to-end test, verify the launch, not the HTTP response code.
The same parameter is what governs how much human involvement remains. With the appropriate alert level configured and auto trigger enabled, the system recommends the most suitable device and dispatches the mission with no human confirmation at all. Set it lower and you keep a confirmation step, which is a reasonable posture for an agency easing into autonomous flight.
Should you hardcode coordinates or map them dynamically?
DJI presents two strategies for the location values, and the right answer depends entirely on how many trigger sources you have.
Option A: static coordinates
If the camera is fixed, hardcode its latitude and longitude straight into the JSON body. This is the easiest way to start and it is the right choice for a proof of concept or a single high-value asset.
Option B: dynamic coordinates
If your VMS or CAD platform supports variables, map the event GPS coordinates into the JSON at trigger time. One workflow then serves alerts from many different locations, which is how this scales past a handful of cameras.
On the VMS side the configuration is a normal event rule. You create the rule, select a trigger such as an intrusion detection or an analytics event from a specific camera, choose HTTP request as the action, paste the FlightHub 2 endpoint into the address field, add the headers, and paste the JSON into the body. Save it and the link is live. From that moment, an intrusion detection fires a web request straight at the drone.
DJI demonstrates this in a VMS, but is clear the steps are universal. Any webhook capable platform works the same way. If your system can send an automated HTTP message when an event occurs, it can fly a drone.
Step fourWhat should the drone do once it arrives?
Here is the design principle that most people miss: the external system only triggers the flight. All of the intelligent behavior is pre-configured in the FlightHub 2 workflow, not in the webhook. Your VMS does not need to know anything about drones.
Inside the workflow you define a flight to waypoint, and then, more importantly, what happens on arrival:
- Orbit the target location automatically for a 360 degree view
- Adjust zoom levels for optimal evidence capture
- Activate the onboard speaker for audio warnings or announcements
- Start recording video and capturing photos, with everything syncing to the cloud automatically
These mission actions are what turn a simple flight to a point into genuine first responder intelligence. A drone that arrives and hovers gives you a static frame. A drone that arrives, orbits, zooms, records, and speaks gives you scene assessment and a deterrent in the same pass. Build the arrival behavior with the same care you would give a patrol briefing.
Can you prove this to stakeholders in 30 minutes?
DJI closes with a checklist framed as a demonstration you can run for stakeholders in under 30 minutes:
- Install your VMS and add a camera
- Configure the FlightHub 2 workflow and get your token
- Connect the two systems via webhook
- Walk in front of the camera to trigger the motion event
That last step is the whole pitch. A person walks past a camera, and a drone leaves a box and flies to them. It is a far more convincing budget argument than any slide, and it is also an honest test, because it exercises every link in the chain: the analytics rule, the HTTP request, the credentials, the alert level, and the mission actions.
Can a police or fire agency actually buy a DJI Dock 3?
This needs a direct answer, because DFR buyers are overwhelmingly public safety agencies. DJI is not NDAA compliant. The Dock 3 and the aircraft that pair with it are not on the Blue UAS list and are not approved for federal procurement. Many state and local agencies still purchase DJI hardware, but a growing number of states restrict it, and any program funded with federal dollars needs to check the rules before it commits.
If your funding source or state statute requires a compliant platform, start with our NDAA compliant drones guide for 2026, which lists the approved manufacturers. If DJI is permitted in your jurisdiction, our Dock 3 versus Autel EVO Nest comparison covers the main docked alternative, noting that Autel is not NDAA compliant either.
What you needThe kit behind a DFR deployment
A DFR program has three layers: the dock, the aircraft, and the software. The dock and aircraft are hardware purchases. FlightHub 2 auto dispatch is the layer that makes them a first responder rather than a scheduled patrol.
| Component | Role in the workflow | Price |
|---|---|---|
| DJI Dock 3 | Weather-sealed drone in a box that houses, charges, and launches the aircraft on command | $15,890 |
| DJI Matrice 4D / 4TD | The aircraft that pair with the Dock 3, the 4TD adding a thermal sensor | Available by quote |
| DJI FlightHub 2 | Hosts the project, the auto dispatch workflow, the token, and every mission action | Subscription, quoted with the system |
| DJI Matrice 4T | Manually flown thermal alternative for agencies not ready to automate dispatch | $7,849 |
Prices last verified August 2026. The Matrice 4T kit at $7,849 already includes the battery, RC Plus 2 controller, charging hub, and case.
The manual comparison is worth taking seriously rather than treating as a lesser option. A Matrice 4T at $7,849 is a capable thermal aircraft that flies when a trained pilot launches it, and for many agencies that is the correct first step. The Dock 3 at $15,890 buys something different: response that does not depend on a human being available. Our Matrice 4 series guide for law enforcement covers the manually flown path in depth.
Frequently asked questions
What does DFR stand for in drone operations?
DFR stands for Drone as First Responder, or in a docked deployment, Dock as First Responder. It means putting an aerial view over an incident the moment it is reported, before ground units arrive, so responders have situational awareness on the way in rather than after they get there.
How fast can a DJI Dock 3 launch after an alert?
DJI states that with parallel dispatch configured across multiple sites, high priority alerts result in drone takeoff in under 15 seconds. That figure covers the automated chain: the third-party system fires the webhook, FlightHub 2 commands the dock, and the aircraft deploys without human confirmation.
Do I need custom software to integrate my VMS with a DJI Dock 3?
No. The integration is a standard HTTP POST, or webhook, and DJI is explicit that no complex middleware is required. Any platform that can send an automated HTTP message when an event occurs can trigger a dispatch, whether that is a video management system, a CAD dispatch system, or a SCADA platform.
Why did my webhook create an alert but not launch the drone?
Almost always the level parameter in the JSON body. Setting level to 4 is what authorizes auto dispatch. If it is not set correctly, the system may only create an alert without launching the aircraft. Check that value before you troubleshoot anything else, because a wrongly leveled request still returns a successful response.
What credentials does FlightHub 2 auto dispatch require?
Three: the project UUID from your project settings, the workflow UUID generated when you create an auto dispatch, and an X user token generated in user settings. The token and project UUID go in the request headers, and the workflow UUID goes in the body.
Can one workflow serve alerts from multiple camera locations?
Yes, if your VMS or CAD system supports variables. Map the event GPS coordinates dynamically into the JSON body instead of hardcoding a single latitude and longitude, and one workflow can serve alerts from many different sites. Coordinates must be in WGS84 format.
Is the DJI Dock 3 NDAA compliant for a public safety agency?
No. DJI is not NDAA compliant and the Dock 3 is not approved for federal procurement. Agencies operating under federal funding rules or state restrictions should review our NDAA compliant drones guide, which lists approved manufacturers such as Skydio, Parrot, Freefly, Inspired Flight, and Teal.
What can the drone do automatically once it reaches the scene?
Mission actions are pre-configured in the FlightHub 2 workflow, not in the triggering system. The aircraft can orbit the target for a 360 degree view, adjust zoom for evidence capture, activate the onboard speaker for audio warnings, and record video and stills, all syncing to the cloud automatically.
Spec a DFR-ready Dock 3 deployment
Tell us your site count, your existing VMS or CAD platform, and your response goals and we will spec the right dock, aircraft, and FlightHub 2 configuration, then send a formal quote. Purchase orders and agency pricing supported.
Request a QuoteRelated reading
- Drones for public safety: platforms, payloads, and program planning
- DJI Dock 3 review: the complete drone-in-a-box guide for 2026
- DJI Dock 3 vs Autel EVO Nest
- DJI Matrice 4 series for police and law enforcement
- Best drones for public safety and first responders in 2026
Video and imagery credit: DJI. Workflow presented by Ferdinand Ma of DJI Enterprise. Global Drone HQ is an authorized DJI enterprise dealer shipping from the United States.
Share:
DJI Matrice 4T vs Matrice 4TD: Which One Should You Choose?
DJI Matrice 4T vs Matrice 4TD: Which One Should You Choose?