Integration
Connect Cartes.io to IP2Location
When something happens in Cartes.io, your agent does the next thing in IP2Location. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Cartes.io and IP2Location 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 Cartes.io and IP2Location
Triggers and actions 2 triggers ยท 13 actions
Trigger
New mapFires when a new map is created.
Trigger
New markerFires when a new marker is added to a map.
Action
Add mapCreate a new map.
Action
Find categoriesSearch for categories matching a query.
Action
Find mapsSearch for maps matching a query.
Action
Get mapRetrieve a single map by ID.
Action
Get map static imageGenerate a static image snapshot of a map.
Action
Get markerRetrieve a single marker by ID.
Action
List categoriesList all available map/marker categories.
Action
List mapsList all maps.
Action
List marker locationsList the recorded location history for a marker.
Action
List markersList all markers on a map.
Action
Get my IP detailsReturns geolocation details for the IP address the request originates from. Takes no IP argument.
Action
Lookup domain WHOISLook up WHOIS registration details for a domain via the IP2WHOIS API (registrar, dates, registrant, nameservers).
Action
Lookup IP geolocationLook up full geolocation, network, proxy and security details for an IP address (IPv4 or IPv6).
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.