Integration

Connect iDigBio to Simpleen Translation

When something happens in iDigBio, 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.

iDigBio1 triggeriDigBio6 actionsSimpleen Translation13 actions

Browse all apps

Build it

What do you want iDigBio 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 Code

Everything your agent can do with iDigBio and Simpleen Translation

Triggers and actions 1 trigger · 19 actions

Trigger
New record
Polls for specimen records newly indexed into iDigBio matching a saved search query, sorted by modified/index date. GET /v2/search/records/ sorted on datemodified.
Action
Find media records
Search iDigBio media records (images/media associated with specimens) matching a query. GET/POST /v2/search/media/ using the iDigBio Query Format (mq/rq parameters).
Action
Find records
Search iDigBio specimen records matching a query. GET/POST /v2/search/records/ using the iDigBio Query Format (rq parameter).
Action
Find recordsets
Search iDigBio recordsets (collections/datasets contributed by publishers) matching a query. GET/POST /v2/search/recordsets/ using the iDigBio Query Format (rsq parameter).
Action
Get media record
Retrieve a single iDigBio media record by its UUID. GET /v2/view/mediarecords/{uuid}.
Action
Get record
Retrieve a single iDigBio specimen record by its UUID. GET /v2/view/records/{uuid}.
Action
Get recordset
Retrieve a single iDigBio recordset (dataset) by its UUID. GET /v2/view/recordsets/{uuid}.
Action
Add glossary
Create a new glossary of word entries/ignored terms for translation. POST /glossaries.
Action
Add segment
Create a new translation segment (source entry + translated entry) tied to a file. POST /segments.
Action
Create Translation
Translates content to selected target language
Action
Get file
Get a specific localization file by id, including its segments and languages. GET /files/{id}.
Action
Get glossary
Get a specific glossary by id, including its entries and ignored words. GET /glossaries/{id}.
Action
Get segment
Get a specific translation segment by id. GET /segments/{id}.
Action
List files
List the localization files known to the account. GET /files.
Action
List glossaries
List the user's glossaries (word lists of ignored terms + custom translations). GET /glossaries.
Action
List languages
List all supported languages (DeepL/Google Translate backed) with source/target flags. GET /languages.
Action
List segments
List translatable segments (source/translated entry pairs) across the user's files. GET /segments.
Action
Run translator
Translate text using a saved, preconfigured Translator (reusable source/target language + format + glossary setup). POST /translators/{id}/translate.
Action
Update glossary
Update an existing glossary's name, entries, or ignored words. PUT /glossaries/{id}.
Action
Update segment
Post-edit an existing translation segment's entry to fix/correct future translation usage. PUT /segments/{id}.

Each app on its own

The other way round: Simpleen Translation to iDigBio