Select to view content in your preferred language

Agentic AI Assistant in ArcGIS Pro for Automated Workflows

1181
6
09-04-2025 08:54 PM
Status: Open
Labels (1)
VenkataKondepati
Regular Contributor

Problem:
ArcGIS Pro has powerful geoprocessing and analysis tools, but many users (especially new analysts, planners, and field teams) struggle to know which tools to chain together, how to set parameters correctly, and how to validate results. Current AI assistants provide guidance or Arcade snippets, but they don’t act on behalf of the user. This leads to long learning curves, errors, and lost productivity.

Enhancement:
Introduce an Agentic AI Assistant in ArcGIS Pro that can:

  1. Understand intent – Parse natural language requests like “Find flood-prone areas within 1 mile of hospitals and rank them by population density.”

  2. Plan workflows – Identify the sequence of geoprocessing tools (e.g., Select Layer by Location → Buffer → Intersect → Summarize Within).

  3. Execute actions – Build and run workflows in ModelBuilder or ArcPy automatically.

  4. Validate outputs – Check for projection mismatches, missing data, or empty outputs and suggest corrections.

  5. Document results – Save workflows as ModelBuilder diagrams or Python scripts, and generate plain-language explanations of what was done and why.

Use Cases:

  • Urban planning: An analyst can ask “Map areas most vulnerable to extreme heat by combining land cover, population density, and proximity to cooling centers.” The Agentic AI plans and executes the workflow, produces a vulnerability map, and saves the script for reuse.

  • Emergency management: During a wildfire event, staff can request “Identify communities within 5 miles of active fire perimeters with elderly population density above threshold.” AI retrieves data layers, buffers perimeters, intersects census data, and returns both maps and reports.

  • Learning & productivity: New GIS staff can learn faster by watching how the AI builds workflows and reviewing the auto-generated ModelBuilder diagram or ArcPy code.

Value:

  • Accessibility: Non-technical staff can use advanced GIS tools without deep training.

  • Speed: Analysts save time on repetitive setup and troubleshooting.

  • Quality: Automated validation reduces human error in geoprocessing.

  • Transparency: Documented workflows improve reproducibility and trust.

6 Comments
SimonSchütte_ct
VenkataKondepati

Hi @SimonSchütte_ct,

Yes. I am looking at it.

Regards,

Venkat

 

AduriSreenivas

 

Subject: Confirmation of supported patterns: ArcGIS Pro ↔ FastAPI/LangChain + ArcGIS Enterprise (incl. Knowledge Graph)

Hello,

We are planning to integrate LangChain + FastAPI with ArcGIS Pro 3.5 using two patterns and would like your confirmation that these are supported:

  1. ArcGIS Pro-authored tools as services:
    • Author geoprocessing tools in ArcGIS Pro and publish as Web Tools / GP services to ArcGIS Enterprise/Server, then invoke them from our FastAPI/LangChain layer over REST (GPServer).
      References: publishing web tools from ArcGIS Pro and calling GP services via REST. ArcGIS Developers+4pro.arcgis.com+4pro.arcgis.com+4
  2. Inside-ArcGIS Pro extensibility calling our API:
    • Build an ArcGIS Pro add-in (and, where applicable, an AI Assistant (beta) custom action) that can call our FastAPI endpoints for LLM/agent tasks and hand results back to Pro.
      References: ArcGIS Pro SDK add-ins (3.5) and AI Assistant note about building custom actions via the Pro SDK. Esri+4pro.arcgis.com+4pro.arcgis.com+4

Additionally, please confirm scope for ArcGIS Enterprise REST—Knowledge Graph (KG):

  • Our services may also call Knowledge Graph over REST (e.g., /knowledgeGraphServer), issuing openCypher queries and retrieving results for downstream reasoning.
    References: KG REST “Graph query” (openCypher) and developer samples. ArcGIS Developers+1

 Proposed Integration Architecture (ArcGIS Pro 3.5):

ArcGIS Pro 3.5

  1. A) Publish GP tools → ArcGIS Enterprise (GPServer/Web Tools) → FastAPI/LangChain calls REST endpoints

(B) Pro add-in / AI Assistant custom action → calls FastAPI (LLM/agents) → returns outputs to Pro/Portal
  └─ (optional) calls ArcGIS Knowledge Graph REST (openCypher)

Could you please confirm that:

  • (1) and (2) are supported patterns for ArcGIS Pro 3.5; and
  • calling ArcGIS Knowledge Graph via Enterprise REST (openCypher) from our service layer is within supported use?

 

Thank you!

Aduri Sreenivas

 

VenkataKondepati

Yes, both patterns are supported.

Pro-authored GP tools → Web Tools/GPServer: Fully supported. You can publish from ArcGIS Pro 3.5 to ArcGIS Enterprise and call those REST endpoints from FastAPI/LangChain.

Pro add-ins / AI Assistant custom actions → FastAPI: Also supported. Pro SDK add-ins and AI Assistant (beta) can call external APIs and return outputs to Pro.

Knowledge Graph REST: Supported. You can query /knowledgeGraphServer with openCypher and use the results downstream.

Your proposed integration architecture aligns with Esri’s supported extensibility and REST patterns.

AduriSreenivas

Hi Venkata Kondepati

Thank you for confirming that the proposed patterns (GP tools as REST services, Pro add-ins / AI Assistant custom actions, and Knowledge Graph REST calls) are supported.

As we move forward, I would appreciate guidance on:

  • Best practices – Are there recommended practices or reference architectures for combining AI orchestration frameworks (e.g., LangChain + FastAPI) with large language models (LLMs) and ArcGIS Pro/ArcGIS Enterprise to enable GeoAI workflows in production?

 

  • AI Assistant custom actions – Since the ArcGIS Pro 3.5 feature is in Beta; are there examples, SDK samples or documentation showing how to build custom actions that call external APIs (beyond the standard add-in samples)?

 

  •   ArcGIS Knowledge Graph integration – When accessing Knowledge Graph via REST and issuing openCypher queries, what performance or scalability considerations (e.g., caching, indexing, query complexity) should be accounted for when integrating with external AI services?

This would help us to build an use case of ArcGIS Pro extensibility + AI orchestration.

 

Thank you!

Aduri Sreenivas

JasmeetSingh1609

Hello @VenkataKondepati @AduriSreenivas @SimonSchütte_ct 
Any luck with graph query? Whenever I try to make use of graph query with data connection pointing to my knowledge graph it fails in AI assistant beta. Details: https://community.esri.com/t5/arcgis-pro-questions/arcgis-pro-ai-assistant-beta-graph-query-returns/...