Integration
Connect Uploadcare to Simpleen Translation
When something happens in Uploadcare, 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 Uploadcare 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 Uploadcare and Simpleen Translation
Triggers and actions 1 trigger · 28 actions
Trigger
New File UploadedTriggers when a new file is uploaded.
- Add file tags
/files/{uuid}/tags/ (add mode) — add tags to a file for organization/AI auto-tagging.
- Add group
/groups/ (Upload API) — create a file group from a set of uploaded file UUIDs.
- Convert document
convert a document/image to another format (e.g. PDF, DOCX to images).
- Convert video
transcode/thumbnail a video file into another format.
- Delete file
delete a file (or POST /files/storage/ for batch delete).
- Delete group
delete a file group (does not delete member files).
- Find files
/files/ with query params — search/filter uploaded files by criteria (used with removed/stored/uploaded_range filters).
- Get file
file info: metadata, size, mime type, URLs.
- Get file metadata
arbitrary key-value metadata attached to a file.
- Get group
file group info: files list, creation date, storage flag.
- List files
return paginated list of uploaded files, with filters (stored, removed, ordering).
- List groups
paginated list of file groups.
- Store file
mark an uploaded file as permanently stored (or POST /files/storage/ for batch store).
- Update file metadata
set/update a metadata key's value on a file.
- Upload File
Upload a new file into your project.
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