Felt for AI agents
Agents read Felt at once. Changes and sends are held for a person's approval by default.
About Felt
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.
What an agent can do in Felt
Every Felt action is classed by the platform as a read, a change or a send. Reads run at once. Changes and sends are held for a person by default.
Runs at once (reads)
Looks things up in Felt without asking first. 7 actions.
- 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 User DetailsTool to retrieve information about the authenticated user. Use after obtaining a valid token to fetch user profile details.
- 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 th
- 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 ma
- 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 inspec
- 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.
- 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
Held for approval by default (changes and sends)
Held for a person's approval by default. The approval is recorded and the action is sent once, never twice, with 10 seconds to undo. 8 actions.
- 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, LineS
- Create ProjectCreate a new Felt project with the specified name and visibility settings. Projects are organizational containers for grouping related maps within a workspace.
- 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.
- 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.
- 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 hav
- Delete ProjectTool to delete a project and all its contents. Use when you need to permanently remove a project after confirmation.
- 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
- Update ProjectTool to update an existing project's name or visibility. Use after confirming the project_id.
Changes wait in Needs you
Changes and sends in Felt are held for a person's approval by default. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
Related connectors
Felt questions
Can an agent change data in Felt on its own?
Not by default. Changes and sends in Felt are held for a person's approval. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
What can an agent read in Felt?
This connector lists 7 read actions. Reads run at once, without waiting for approval.
How does Felt connect?
It connects with API key. Connectors are built and maintained by third-party developers; availability is confirmed during scoping.