Integration
Connect Mapulus to Exchangerate.dev
When something happens in Mapulus, your agent does the next thing in Exchangerate.dev. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want Mapulus and Exchangerate.dev 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 Mapulus and Exchangerate.dev
Triggers and actions 2 triggers ยท 9 actions
Trigger
New LocationTriggers when a new location is added in Mapulus.
Trigger
New MapTriggers when a new map is created in Mapulus.
Action
Create LocationAdds a location pin to a layer on a Mapulus map, from an address or from coordinates.
Action
Delete LocationRemoves a location pin from a Mapulus map.
Action
Find LocationReturns Mapulus locations, optionally limited to one map or to the location with a given external ID.
Action
Find MapReturns the maps in your Mapulus account, so you can pick the one to add locations to.
Action
Update LocationUpdates a location pin in Mapulus. Only the fields you supply are changed.
Action
Convert currencyConverts an amount from one currency to another using current rates. GET /v1/convert/{from_ccy}/{to_ccy}/{amount} or /v1/convert/{from_ccy}/{to_ccy}
Action
Get exchange rateReturns the exchange rate for a specific currency pair slug. GET /v1/rate/{slug}
Action
Get historical exchange ratesReturns exchange rates for a specific past date, optionally for a given base currency. GET /v1/{date} or GET /v1/{date}/{path_base}
Action
List exchange rate rangeReturns exchange rates across a date range for a base currency. GET /v1/range
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.