ceven

Felt

Syncs geospatial data from your SaaS tools directly onto interactive maps, manages project layers based on real time alerts, and automates the creation of map elements from external data sources.

Try Felt in Ceven

Ask Ceven anything
Standard

Why use Ceven?

  1. AI native Felt integration

    • Describe the outcome and Ceven picks the right Felt calls, fills the parameters, and checks the result.
    • Structured, agent friendly tool schemas so each call runs reliably instead of by guesswork.
    • Rich coverage for reading, writing, and querying your Felt data, across all 15 of its actions.

  2. Managed auth

    • Built in OAuth with automatic token refresh and rotation.
    • One place to manage, scope, and revoke Felt access.
    • Per user and per environment credentials instead of shared keys.

  3. Agent optimized design

    • Actions are tuned from real success and error rates so reliability climbs over time.
    • Full execution logs so you always know what ran in Felt, when, and on whose behalf.
    • The agent pauses and asks when Felt is unclear instead of plowing ahead.

  4. Enterprise grade security

    • Fine grained access so you control which agents and people can reach Felt.
    • Least privilege by default, read scopes first and only the writes a workflow needs.
    • A full audit trail of every Felt action to support review and sign off.

Supported tools

Every action Ceven's agents can run on Felt, and when to use it.

Create or Update Elements
Use this when you need to batch add or modify elements on a specified map using a GeoJSON feature collection.
Create Project
Use this when you need to initialize a new project with a specific name and optional description.
Delete Element
Use this when you have both map and element ids and need to remove the element permanently.
Delete Layer
Use this when you have the map and layer ids and need to remove the layer permanently.
Delete Map
Use this when you have the map id and want to permanently remove it from the account.
Delete Project
Use this when you need to permanently remove a project and all its contained contents.
Duplicate Map
Use this when you need a clone of an existing map to use as a starting point for new work.
Get Map Details
Pull full map metadata using a valid map id to understand current settings and properties.
Get User Details
Pull the profile details of the authenticated user to verify account permissions.
List Element Groups
Enumerate all grouped elements on a specific map after confirming the map id.
List Elements
Retrieve all elements on a specific map as GeoJSON features for analysis or migration.
List Layers
Pull a list of all layers on a specific map to organize visibility and ordering.
List Projects
Browse or select from existing projects accessible to the user.
List Sources
Enumerate all available data sources before selecting one for a map import.
Update Project
Modify an existing project name, description, or custom properties after confirming the project id.
Create Felt Project
Tool to create a new felt project. use when you need to initialize a project with a specific name and optional description or organization context.

16 actions · scroll to see them all

Frequently asked questions

Ceven processes large spatial datasets by chunking the GeoJSON feature collection into smaller batches before calling the Create or Update Elements tool. This prevents timeout errors and ensures that the Felt API can ingest the data without dropping features. The agent tracks the progress of each batch and notifies you once the entire set is plotted. If a specific feature contains invalid geometry that Felt cannot render, the agent captures the error for that specific element and continues with the rest of the set, providing a summary of any failed points at the end of the workflow.
Ceven interacts with Felt via the authenticated user token, meaning it can perform any action the connected user is authorized to do. While it can create projects and maps, the fine grained sharing permissions are typically handled within the Felt UI. However, the agent can automate the organizational side by creating projects within specific organization contexts if the API supports it. If you need to restrict who sees a map, you should set the default project visibility in Felt first, and the agent will respect those settings when it initializes new projects for your team.
If a user manually deletes an element in the Felt interface and the agent subsequently tries to update it using a stored element id, the API will return a not found error. Ceven handles this gracefully by treating the update as a request to recreate the element. The agent will use the existing GeoJSON data to push a new element to the map and then update its internal reference to the new element id. This ensures that your automated workflows do not break when humans make manual edits to the map in real time.
Felt imposes certain limits on the number of elements per map to maintain performance. A key quirk of the Felt API is that very large feature collections can trigger rate limits or lead to slower rendering times in the browser. Ceven monitors the API response headers for rate limit warnings and will automatically implement an exponential backoff strategy to avoid being throttled. For extremely large datasets, we recommend using the agent to organize data into multiple layers or separate maps to ensure the Felt interface remains responsive for your end users.
Currently, the Felt integration is primarily focused on pushing data into Felt and managing map structures. Because Felt does not provide a generic webhook system for every element movement or property change, Ceven cannot trigger a workflow the instant a user drags a point on the map. Instead, you can set up a scheduled polling workflow where the agent uses the List Elements tool to check for changes in element properties or positions and then triggers downstream actions in your other SaaS tools based on those spatial changes.
Yes, Ceven supports the standard GeoJSON types that Felt accepts, including Points, LineStrings, and Polygons. When you provide data to the agent, it ensures the geometry is correctly formatted as a FeatureCollection before sending it to the Felt API. If you provide a list of addresses or coordinates, the agent can handle the conversion into the required GeoJSON format automatically. This allows you to pull simple latitude and longitude pairs from a spreadsheet and have them appear as professional map markers without needing to write your own spatial conversion code.
The Duplicate Map action creates an exact copy of an existing map, including all its elements and layers. This is particularly useful for creating templates. For example, you can have a master template map with all the standard city boundaries and utility markers. When a new project starts, the agent duplicates that template, renames the new map to the specific project name, and then adds the project specific data elements. This ensures consistency across all your mapping projects while avoiding the need to rebuild the base layers from scratch every single time.
Ceven uses a secure token based authentication system to connect to your Felt account. When you first link the account, you provide the necessary credentials or authorize via the Felt consent flow. This token is stored using industry standard encryption and is only used to make requests on your behalf. You can revoke this access at any time through your Felt account settings. Once revoked, all active Ceven workflows that rely on the Felt integration will stop immediately until a new token is provided and authorized by an account administrator.

Alternatives to Felt

Other tools that solve a similar problem. Ceven supports these too, so you can switch or run more than one at once.

ArcGIS logoArcGISMapbox logoMapboxCarto logoCarto

Try Ceven on your stack

Plug Ceven on top of the tools you already run. Connect Felt and the rest of your stack, describe the outcome, and its agents handle the work end to end, days of it in minutes.

Get started for free