Integration
Connect Zamzar to Simpleen Translation
When something happens in Zamzar, 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 Zamzar 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 Zamzar and Simpleen Translation
Triggers and actions 2 triggers ยท 22 actions
Trigger
New Conversion JobTriggered when a new conversion job is created in your Zamzar account.
Trigger
New FileTriggered when a new file appears in your Zamzar account, whether uploaded or produced by a conversion.
Action
Convert FileStarts a Zamzar conversion job that converts a file you supply into another format. Returns the new job with its id and status so you can check on it or collect the converted file later.
Action
Create Content FileCreates a file on Zamzar from text content you supply, so it can be converted or downloaded later. Returns the stored file with its id, name and size.
Action
Delete conversion jobDeletes a conversion job from Zamzar. Returns the job that was removed.
Action
Delete fileDeletes a file stored on Zamzar. Returns the file that was removed.
Action
Find Converted FileLooks through the files stored on Zamzar and returns the ones whose name matches the text you supply. Use it to locate a converted file after a conversion job has finished.
Action
Get conversion jobReturns a single Zamzar conversion job, including its current status and any converted files it produced.
Action
Get fileReturns the details of a single file stored on Zamzar, including its name, format and size.
Action
List conversion jobsReturns the conversion jobs in your Zamzar account, most recent first.
Action
List formatsReturns every source format Zamzar can convert from, along with the target formats each one can be converted into.
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.