Fire departments that run FirstDue can now connect that data directly to FlorianAI. The integration is live: FlorianAI reads the pre-plans, occupancy records, dispatch data, and incident documentation your department already maintains in FirstDue and surfaces it alongside your staffing, training, and institutional knowledge, where operational decisions actually happen. Battalion chiefs and company officers get answers that span systems without opening a second login. The connection runs on your department's own FirstDue API credentials, requires nothing from FirstDue's side, and adds no new contract to your procurement stack.
What Data Does FirstDue Hold That Fire Chiefs Need Operationally?
FirstDue is where many departments keep the pre-incident side of their operational picture. Through its REST API, FirstDue exposes the data domains that matter most on a call and in the planning cycle: dispatch records, incident report notifications, pre-fire plans and caution notes, premises records with their inspectable systems and equipment inventories, and live responder unit status.
Each of those domains carries weight on its own. Dispatch records hold the call history for every address in the response area. Pre-fire plans and caution notes hold what a crew needs in front of them in the first minutes of a response: the standpipe location, the hazardous material storage, the access constraint that changes how the first-due engine positions. Premises records track the inspectable systems in each building, from standpipes to elevators, along with the equipment inventories tied to them. Responder unit status shows which apparatus are committed right now. Taken together, this is the operational memory of a department's prevention and response work, accumulated over years of inspections, pre-planning, and calls.
That data is operationally critical and, for most departments, operationally stranded. The pre-plan for a high-risk occupancy lives in FirstDue. The roster showing who covers that occupancy tonight lives in your scheduling system. The training history that says whether that crew has worked that occupancy type lives in a third platform. Each record is accurate inside its own system, and no system can read the others.
The result is a familiar routine: a battalion chief building tomorrow's coverage picture opens FirstDue for the pre-plan and premises data, the scheduling tool for the roster, the training platform for certifications, and a spreadsheet to hold it all together. The data exists. The connection between it does not.
How FlorianAI Connects to FirstDue via API
FirstDue provides REST API access to the data a department has built in its platform. FlorianAI connects to that API using credentials your department provides, then reads FirstDue's data into the same operational layer where your staffing, training, and incident history already live.
To be clear about what this is: FlorianAI is not a formal integration partner or certified vendor of FirstDue. This is an API-based connection available to FlorianAI customers who use FirstDue and choose to provide API credentials. No action is required from FirstDue. No new contract or agreement with them is needed.
The mechanics are straightforward. FirstDue's API uses token-based authentication: your department's API credentials generate a bearer token, and FlorianAI handles the token lifecycle on the backend. FirstDue's API also supports scoped permissions, so a department can grant access at the level its data governance requires, for example a read permission limited to dispatch records. FlorianAI uses only the API's read operations. It does not create, modify, or delete anything in your FirstDue account.
Setup works like this:
Your department provides FlorianAI with FirstDue API credentials
FlorianAI configures the connection on the backend
FirstDue's pre-plan, dispatch, and incident data begins appearing in your FlorianAI interface
Nothing gets migrated. Nothing gets re-entered. The inspection cycle, occupancy records, and pre-plan library your department built in FirstDue stay exactly where they are. FlorianAI reads them where they live.
What Fire Chiefs Can See With the Combined Data
When FlorianAI reads FirstDue's data alongside the rest of your stack, cross-system questions become single questions.
Which caution notes apply to the addresses your crews were dispatched to in the last 30 days? FlorianAI can tell you. Which premises carry inspectable systems that are overdue against their inspection cycle, and what does the dispatch history at those addresses look like since the last inspection? FlorianAI can tell you. Which caution notes are set to expire this quarter, and which of those addresses have active dispatch history? FlorianAI can tell you.
None of that requires a report builder, an export routine, or a request to whoever administers the FirstDue account. The question gets asked in plain language, and FlorianAI reads the FirstDue data your department granted access to against the staffing, training, and incident history it already connects to.
The same connected read applies to incident documentation. FlorianAI's NERIS integration already pre-populates operational run reports from CAD and RMS data. According to the U.S. Fire Administration, NERIS requires more structured data capture than NFIRS did, and FirstDue's incident records are one more source that structured workflow can draw on instead of asking a company officer to rebuild the picture by hand.
This is the pattern that matters for growing departments. A department like Springdale, Arkansas Fire Department, with 170 firefighters and roughly 65% of personnel under five years of experience, holds its operational picture across more systems every year. The faster a department grows, the more valuable it is to read those systems together rather than one login at a time. For the full breakdown of what FlorianAI adds for departments running FirstDue, see Fire Departments Using FirstDue: What FlorianAI Adds to the Picture.
Does This Require IT or a New Contract With FirstDue?
No new vendor agreement is required. FirstDue is already in your stack, and the connection uses credentials your department already controls. The scoped-permission model means your department decides exactly which FirstDue data FlorianAI can read, which is usually the first question a city IT reviewer asks. And because the connection is token-based rather than a standing password share, access is issued in limited-lifetime tokens that FlorianAI renews through the API, the same authentication pattern IT reviewers see from every modern vendor connection they approve.
For departments that have already completed a formal IT or procurement review to bring in FlorianAI, this connection does not add a new vendor to that process. For departments still working through approval, the integration is worth raising explicitly: it demonstrates that FlorianAI is built to work with the platforms you already run, not replace them. If your city's review process is the current hurdle, we wrote a guide on getting FlorianAI approved through IT and security review.
What About Departments That Do Not Use FirstDue?
If your department does not run FirstDue, this specific connection does not apply, but the underlying capability is the same. FlorianAI, an AI operations assistant built for fire departments, is designed to read across the systems a department already runs: everything from RMS, CAD, and scheduling to training platforms like Vector Solutions, NERIS incident reporting, and more. The NERIS and Vector Solutions integrations are live today, FirstDue joins them now, and the roadmap is driven by what departments are actually running. Every new connection follows the same principle: your data stays in the system that owns it, and FlorianAI reads it where it lives.
If your department uses a different platform for pre-plans, inspections, or incident documentation and you want to understand what a FlorianAI connection would look like for your stack, schedule a demo and we can walk through it.
Frequently Asked Questions
Q: Is this an official partnership with FirstDue?
A: No. FlorianAI connects to FirstDue's REST API using credentials provided by the fire department. This is a customer-enabled connection, not a formal integration partnership or certified product integration with FirstDue.
Q: What credentials are needed to enable the connection?
A: Your department's FirstDue API credentials, which generate a token-based connection. FlorianAI handles configuration and the token lifecycle on our end after you provide them. FirstDue's scoped permissions let your department limit access to specific data domains.
Q: Will enabling this connection change our FirstDue data?
A: No. FlorianAI uses only the API's read operations. It does not create, modify, or delete records in your FirstDue account.
Q: Do we still need our FirstDue subscription if we add FlorianAI?
A: Yes. The connection depends on it. FirstDue keeps doing what it does: occupancy management, inspections, pre-plans, and its own reporting workflows. FlorianAI reads that data alongside the rest of your stack and answers the cross-system questions no single platform can.
Q: Is this available to all FlorianAI customers?
A: The FirstDue connection is available to FlorianAI customers whose departments use FirstDue. If you are a current customer, reach out and we will configure it. If you are evaluating FlorianAI and FirstDue is in your stack, this is worth factoring into your review.