Mapulus is a platform that enables users to create, manage, and analyze interactive maps, integrating with various applications to automate tasks and leverage location insights.
Mapulus is a platform that enables users to create, manage, and analyze interactive maps, integrating with various applications to automate tasks and leverage location insights. On Nagent, Mapulus is exposed as a fully-configurable developer tools integration that any agent can call — 3 actions, and API key authentication. No code is required to wire Mapulus into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Mapulus 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 Mapulus 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 Mapulus, with input parameters and output schema. Drop these into any step of an agent built in Helix.
MAPULUS_FIND_LOCATION_WITH_EXTERNAL_IDFind locations by their external identifier. Returns a list of locations that match the provided external_id. External IDs are unique identifiers used for integrating Mapulus with external systems (CRM, databases, etc.). Returns an empty list if no matching locations are found.
Input parameters
External identifier used to find matching location(s). This is a unique identifier assigned to locations for external system integration.
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
MAPULUS_GET_MAP_DETAILSTool to retrieve detailed information about a map. Use when you have a map_id and need full map metadata.
Input parameters
The unique identifier of the map to retrieve
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
MAPULUS_LIST_MAPSRetrieves a paginated list of all maps accessible to the authenticated user. Supports filtering by name/tag and sorting by various fields. Returns map metadata including IDs, titles, and timestamps. Use this to discover available maps before fetching detailed information or locations.
Input parameters
Filter maps by a specific tag (exact match). Returns only maps that have this exact tag.
Filter maps by title using partial text match (case-insensitive). Returns maps whose title contains this text.
Page number to retrieve (starting from 1). Leave empty to get the first page.
Field name to sort results by. Common values: 'title', 'created_at', 'updated_at'. Defaults to 'created_at' if not specified.
Number of maps to return per page (1-100). Leave empty for API default (typically 50).
Sort direction: 'asc' for ascending (A-Z, oldest first) or 'desc' for descending (Z-A, newest first). Defaults to 'desc'.
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 47 agents privately built on Nagent that already use Mapulus.
Build on Nagent
Connect Mapulus 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 Mapulus, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Mapulus is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Mapulus is connected, you configure its 3 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Mapulus 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 Mapulus event fires, the agent kicks off automatically.
Every Mapulus 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 Mapulus ships with 3 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Mapulus together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Mapulus-based workflows tailored to your business.