Integration
Connect QuintaDB to Simpleen Translation
When something happens in QuintaDB, 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 QuintaDB 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 QuintaDB and Simpleen Translation
Triggers and actions 7 triggers ยท 23 actions
Trigger
New DatabaseTriggers when a new database is created in the connected QuintaDB account.
Trigger
New FormTriggers when a new form is added to a QuintaDB database.
Trigger
New Form FieldTriggers when a new field is added to a QuintaDB form.
Trigger
New or Updated RecordTriggers when a record in a QuintaDB form is added or changed.
Trigger
New RecordTriggers when a new record is added to a QuintaDB form.
Trigger
New Table RecordTriggers when a new record is added to a QuintaDB form.
Trigger
New Table ReportTriggers when a new report is created on a QuintaDB form.
Action
Add formAdds a new form (table) to a QuintaDB database. Returns the created form.
Action
Create RecordAdds a new record to a QuintaDB form. The form's own fields are offered for mapping, and the created record's id is returned.
Action
Delete formDeletes a form (table) and its records from a QuintaDB database.
Action
Delete RecordDeletes a record from a QuintaDB form.
Action
Delete recordsDeletes several records from a QuintaDB form in one call.
Action
Find RecordsReturns the records in a QuintaDB form that match the conditions you specify.
Action
Get recordReturns one record from a QuintaDB form, including all of its field values.
Action
Update CellChanges the value of one field on one QuintaDB record.
Action
Update RecordChanges field values on an existing QuintaDB record. Fields you leave blank keep their current value.
Action
Upload fileUploads a file into a file field on an existing QuintaDB record.
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.