Integration
Connect Cakemail to Simpleen Translation
When something happens in Cakemail, 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 Cakemail 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 Cakemail and Simpleen Translation
Triggers and actions 8 triggers ยท 15 actions
Trigger
New ContactTriggers when a new Contact is added.
Trigger
New Email BounceTriggers when an email bounces.
Trigger
New Email ClickTriggers when a new Email Click is tracked.
Trigger
New Email OpenTriggers when a new Email Open is tracked.
Trigger
New ListTriggers when a List is created.
Trigger
New Suppressed EmailTriggers when a new Suppressed Email is added.
Trigger
Unsubscribed ContactTriggers when a Contact is unsubscribed.
Trigger
Updated ContactTriggers when a Contact is updated.
Action
Add Suppressed EmailAdds an email address to the Cakemail suppression list so no further mail is sent to it.
Action
Find Contact by EmailReturns the contacts on a Cakemail list whose email address matches the one you supply.
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.