Integration
Connect Langfuse to Simpleen Translation
When something happens in Langfuse, 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 Langfuse 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 Langfuse and Simpleen Translation
Triggers and actions 1 trigger ยท 26 actions
Trigger
New TracePolling trigger: fires for newly created traces (dedup by trace id / timestamp). GET /api/public/traces
Action
Add CommentAdd a comment to a trace/observation/session/prompt object. POST /api/public/comments
Action
Add DatasetCreate a new dataset. POST /api/public/v2/datasets
Action
Add Dataset ItemCreate an item (input/expected_output/metadata) in a dataset. POST /api/public/dataset-items
Action
Add PromptCreate a new prompt version (text or chat). POST /api/public/v2/prompts
Action
Add ScoreCreate a score attached to a trace/observation/session (numeric, categorical, or boolean). POST /api/public/scores
Action
Delete TraceDelete a trace by id. DELETE /api/public/traces/{traceId}
Action
Get ProjectReads the Langfuse project that the connection's project-scoped API key belongs to.
Action
Get PromptGet a prompt by name (and optional version/label). GET /api/public/v2/prompts/{promptName}
Action
Get TraceGet a single trace by id, including nested observations/scores. GET /api/public/traces/{traceId}
Action
List Dataset ItemsList items in a dataset. GET /api/public/dataset-items
Action
List DatasetsList all datasets in the project. GET /api/public/v2/datasets
Action
List PromptsList all prompts in the project. GET /api/public/v2/prompts
Action
List ScoresList scores with optional filters. GET /api/public/v2/scores
Action
Add glossaryCreate a new glossary of word entries/ignored terms for translation. POST /glossaries.
Action
Add segmentCreate a new translation segment (source entry + translated entry) tied to a file. POST /segments.
Action
Create TranslationTranslates content to selected target language
Action
Get fileGet a specific localization file by id, including its segments and languages. GET /files/{id}.
Action
Get glossaryGet a specific glossary by id, including its entries and ignored words. GET /glossaries/{id}.
Action
Get segmentGet a specific translation segment by id. GET /segments/{id}.
Action
List filesList the localization files known to the account. GET /files.
Action
List glossariesList the user's glossaries (word lists of ignored terms + custom translations). GET /glossaries.
Action
List languagesList all supported languages (DeepL/Google Translate backed) with source/target flags. GET /languages.
Action
List segmentsList translatable segments (source/translated entry pairs) across the user's files. GET /segments.
Action
Run translatorTranslate text using a saved, preconfigured Translator (reusable source/target language + format + glossary setup). POST /translators/{id}/translate.
Action
Update glossaryUpdate an existing glossary's name, entries, or ignored words. PUT /glossaries/{id}.
Action
Update segmentPost-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.