> For the complete documentation index, see [llms.txt](https://support.airspacelink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.airspacelink.com/setup-integrations-and-customizations/servicenow-work-order-fsm-integration.md). # ServiceNow Work Order (FSM) Integration Connect AirHub® Portal to ServiceNow Field Service Management (FSM) for two-way work order sync. Drone work requests created in ServiceNow flow directly into AirHub® Portal as work orders, and status updates, work notes, and deliverables from AirHub® flow back to the originating ServiceNow record. #### Who this is for This integration is for ServiceNow customers with Field Service Management (FSM) licensed. If your ServiceNow instance does not have FSM, see the ServiceNow Catalog Integration guide instead, which uses the Service Catalog to provide the same end-to-end workflow. #### License Requires Team License or higher. #### Installation Install the integration through the ServiceNow Store: AirspaceLink Drone Flight Request (AirHub® Portal Integration) on ServiceNow Store → The Store listing includes the app description, prerequisites, supported ServiceNow versions, and install instructions. After installation, contact to register your ServiceNow instance with AirHub® Portal and complete the activation. --- # 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://support.airspacelink.com/setup-integrations-and-customizations/servicenow-work-order-fsm-integration.md?ask= ``` 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.