Felt is a modern GIS platform that allows users to create, modify, and share interactive maps, integrating powerful mapping capabilities into various workflows and applications.
Felt is a modern GIS platform that allows users to create, modify, and share interactive maps, integrating powerful mapping capabilities into various workflows and applications. On Nagent, Felt is exposed as a fully-configurable developer tools integration that any agent can call — 15 actions, and API key authentication. No code is required to wire Felt into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Felt to automate the kinds of tasks developer tools teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Felt into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Felt, with input parameters and output schema. Drop these into any step of an agent built in Helix.
FELT_CREATE_OR_UPDATE_ELEMENTSCreate or update map elements using GeoJSON FeatureCollection format. Creates new elements by default; to update existing elements, include 'felt:id' in the feature's properties. Supports Point, LineString, Polygon, and Multi-type geometries. Returns the created/updated elements with assigned IDs and Felt-specific properties.
Input parameters
Must be 'FeatureCollection'
Unique identifier of the map to modify
Array of GeoJSON Feature objects representing elements to create or update
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FELT_CREATE_PROJECTCreate a new Felt project with the specified name and visibility settings. Projects are organizational containers for grouping related maps within a workspace.
Input parameters
The name to be used for the Project.
Project visibility: "workspace" (viewable by all members of the workspace) or "private" (only viewable by invited users).
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FELT_DELETE_ELEMENTTool to delete a specific element from a map. Use when you have both map and element IDs and need to remove the element permanently.
Input parameters
The unique identifier of the map containing the element to delete.
The unique identifier of the element to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FELT_DELETE_LAYERTool to delete a specific layer from a map. Use when you have the map's and layer's IDs and need to remove it permanently.
Input parameters
The unique identifier of the map containing the layer to delete.
The unique identifier of the layer to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FELT_DELETE_MAPPermanently deletes a map and all its associated data from Felt. WARNING: This action cannot be undone. The map and all its layers, elements, and comments will be permanently removed. Use when you have the map's ID and need to permanently remove it. Returns no content (HTTP 204) on success.
Input parameters
The unique identifier of the map to delete.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FELT_DELETE_PROJECTTool to delete a project and all its contents. Use when you need to permanently remove a project after confirmation.
Input parameters
The ID of the project to be deleted.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FELT_DUPLICATE_MAPCreates a complete copy of a Felt map including all layers, elements, and configuration. Use when you need to clone an existing map to a new location or create a template-based map. The duplicated map can optionally be placed in a specific project or folder.
Input parameters
Optional title for the duplicated map. If not provided, defaults to '\[Original Title\] (copy)'
Unique identifier of the map to duplicate
Destination configuration for the duplicated map. Must specify either project_id or folder_id.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FELT_GET_MAP_DETAILSRetrieves comprehensive details of a specific Felt map including title, URL, layers, elements, basemap settings, access permissions, and timestamps. Requires a valid map ID. Use this when you need to: - Get complete map configuration and metadata - Access map layers and elements - Check map permissions and access settings - Retrieve map URLs for sharing
Input parameters
Unique identifier for the map to retrieve. Format: alphanumeric string (e.g., 'TJRl4cNyS12T5z8qM3JRnA')
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FELT_GET_USER_DETAILSTool to retrieve information about the authenticated user. Use after obtaining a valid token to fetch user profile details.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FELT_LIST_ELEMENT_GROUPSRetrieves all element groups from a Felt map. Element groups are collections of geographic features (points, lines, polygons) organized together. Each group returns a GeoJSON FeatureCollection with the group's elements, along with styling properties like color and symbol. Use this when you need to discover what element groups exist on a map or access grouped geographic data.
Input parameters
The unique identifier for the map.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FELT_LIST_ELEMENTSLists all elements on a specific map as a GeoJSON FeatureCollection. Returns elements that are not in element groups. Use when you need to retrieve the map's direct elements after obtaining a valid map_id.
Input parameters
Unique identifier of the map to list elements from. Elements not in element groups will be returned.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FELT_LIST_LAYERSTool to list all layers on a specific map. Returns all layers present on the map with their complete metadata including status, geometry type, styling, and attributes. Use this when you need to inspect or enumerate the data layers on a map.
Input parameters
The unique identifier for the map.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FELT_LIST_PROJECTSTool to retrieve a list of projects accessible to the user. Use when you need to browse or select from existing projects before proceeding.
Input parameters
Workspace ID to filter projects for a specific workspace
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FELT_LIST_SOURCESList all data sources (external data connections) accessible to the authenticated user. Sources represent connections to external data providers like BigQuery, PostgreSQL, S3, Snowflake, etc. Use this to discover available sources before importing data from them into Felt maps. Each source includes sync status, connection type, and access permissions.
Input parameters
Filter sources by workspace ID. Only needed when using the API as part of a plugin.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
FELT_UPDATE_PROJECTTool to update an existing project's name or visibility. Use after confirming the project_id.
Input parameters
The new name for the project
ID of the project to update
Project visibility: 'workspace' (viewable by all workspace members) or 'private' (only invited users)
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 87 agents privately built on Nagent that already use Felt.
Build on Nagent
Connect Felt to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Felt, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Felt is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Felt is connected, you configure its 15 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Felt steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Felt event fires, the agent kicks off automatically.
Every Felt action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Felt ships with 15 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Felt together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Felt-based workflows tailored to your business.