Integration
Connect Mapulus to Simpleen Translation
When something happens in Mapulus, your agent does the next thing in Simpleen Translation. 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 Simpleen Translation 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 Simpleen Translation
Triggers and actions 2 triggers ยท 18 actions
Trigger
New LocationTriggers when a new location is added in Mapulus.
- New Map
Triggers when a new map is created in Mapulus.
- Create Location
Adds a location pin to a layer on a Mapulus map, from an address or from coordinates.
- Delete Location
Removes a location pin from a Mapulus map.
- Find Location
Returns Mapulus locations, optionally limited to one map or to the location with a given external ID.
- Find Map
Returns the maps in your Mapulus account, so you can pick the one to add locations to.
- Update Location
Updates a location pin in Mapulus. Only the fields you supply are changed.
Action
Add glossaryCreate a new glossary of word entries/ignored terms for translation. POST /glossaries.
- Add segment
Create a new translation segment (source entry + translated entry) tied to a file. POST /segments.
- Create Translation
Translates content to selected target language
- Get file
Get a specific localization file by id, including its segments and languages. GET /files/{id}.
- Get glossary
Get a specific glossary by id, including its entries and ignored words. GET /glossaries/{id}.
- Get segment
Get a specific translation segment by id. GET /segments/{id}.
- List files
List the localization files known to the account. GET /files.
- List glossaries
List the user's glossaries (word lists of ignored terms + custom translations). GET /glossaries.
- List languages
List all supported languages (DeepL/Google Translate backed) with source/target flags. GET /languages.
- List segments
List translatable segments (source/translated entry pairs) across the user's files. GET /segments.
- Run translator
Translate text using a saved, preconfigured Translator (reusable source/target language + format + glossary setup). POST /translators/{id}/translate.
- Update glossary
Update an existing glossary's name, entries, or ignored words. PUT /glossaries/{id}.
- Update segment
Post-edit an existing translation segment's entry to fix/correct future translation usage. PUT /segments/{id}.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews