Integration
Connect BotMape to Geocode.xyz
When something happens in BotMape, your agent does the next thing in Geocode.xyz. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want BotMape and Geocode.xyz to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with BotMape and Geocode.xyz
Triggers and actions 1 trigger · 13 actions
Trigger
New Lead CapturedTriggers when a new lead is captured — either from a chat conversation or added manually.
- Add agent
Create a new AI agent with custom configuration and personality. POST /api/chatbots
- Add knowledge base entry
Add training content (FAQ, documentation, policies) to an AI agent; auto-embedded. POST /api/chatbots/:chatbotId/knowledge
- Create Lead
Creates a new lead in your CRM. Use this to push leads from other tools into your CRM automatically.
- Delete knowledge base entry
Remove a specific knowledge entry from an AI agent's training data. DELETE /api/chatbots/:chatbotId/knowledge/:knowledgeId
- Get agent
Retrieve detailed information about a specific AI agent by ID. GET /api/chatbots/:id
- List agents
Get all AI agents owned by the authenticated user with their configurations. GET /api/chatbots
- List knowledge base entries
Retrieve all knowledge base entries that train an AI agent's responses. GET /api/chatbots/:chatbotId/knowledge
- Update agent
Update an existing AI agent's configuration, personality, or appearance. PUT /api/chatbots/:id
Action
Autocomplete addressGet street name, city, and postal code suggestions for a partial street name, city name, or postal code within a given region. GET https://geocode.xyz/?region={region}&streetname={partial}&cityname={partial}&geoit=json
- Geocode address
Convert a street address, postal code, landmark, or city name into latitude/longitude coordinates (forward geocoding). GET https://geocode.xyz/?locate={address}&json=1
- Geolocate IP address
Look up the approximate physical location of an IP address. GET https://geocode.xyz/?locate={ip_address}&json=1
- Geoparse text
Scan a block of free text and extract every place name mentioned, geocoded to coordinates and ordered by match confidence. POST https://geocode.xyz/ with scantext={text}&json=1
- Reverse geocode coordinates
Convert a latitude,longitude point into the nearest street address description (reverse geocoding). GET https://geocode.xyz/?locate={lat},{lng}&json=1
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.