Integration

Connect inspirehep.net to Simpleen Translation

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

inspirehep.net2 triggersinspirehep.net7 actionsSimpleen Translation13 actions

Browse all apps

Build it

What do you want inspirehep.net 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 inspirehep.net and Simpleen Translation

Triggers and actions 2 triggers · 20 actions

Trigger
New job posting
Fires when a new physics job posting is added to INSPIRE matching a search query. Polls the jobs search endpoint sorted by most recent.
Trigger
New literature
Fires when a new literature (paper) record is added to INSPIRE matching a search query. Polls the literature search endpoint sorted by most recent.
Action
Find authors
Search INSPIRE for author records matching a query (name, affiliation, etc).
Action
Find jobs
Search INSPIRE for physics job postings matching a query.
Action
Find literature
Search INSPIRE's literature database for papers matching a query (title, author, arXiv id, DOI, etc).
Action
Get author
Retrieve a single author record by its INSPIRE record id or ORCID iD.
Action
Get conference
Retrieve a single conference record by its INSPIRE record id.
Action
Get institution
Retrieve a single institution record by its INSPIRE record id.
Action
Get literature
Retrieve a single literature (paper) record by its INSPIRE record id, DOI, or arXiv id.
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 inspirehep.net