Integration
Connect Manifestly Checklists Agent to Simpleen Translation
When something happens in Manifestly Checklists Agent, 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 Manifestly Checklists Agent 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 Manifestly Checklists Agent and Simpleen Translation
Triggers and actions 1 trigger ยท 18 actions
Trigger
Run LateTriggers when a run is late.
- Change Step State
Completes, reopens, skips, starts, stops or stores data on a step of a Manifestly checklist run.
- Get Run
Look up one checklist run by its id and return its current details, including its title, state, progress, notes, tags and the workflow it came from.
- List Run Steps
Returns the steps of a checklist run
- List Workflows
Returns the checklist workflows in your Manifestly account.
- Run Workflow
Starts a new run of a Manifestly checklist workflow, optionally naming it, scheduling it and assigning the people who take part.
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