Integration
Connect Nutshell to Simpleen Translation
When something happens in Nutshell, 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 Nutshell 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 Nutshell and Simpleen Translation
Triggers and actions 6 triggers ยท 25 actions
Trigger
Activity LoggedTriggers when an Activity is logged.
Trigger
Lead WonTriggers when a lead is won.
Trigger
New ActivityTriggers when new Activity is created.
Trigger
New CompanyTriggers when new Company is created.
Trigger
New LeadTriggers when a new Lead is created.
Trigger
New PersonTriggers when new Person is created.
Action
Create CompanyCreates a new Company.
Action
Create LeadCreates a new Lead.
Action
Create PersonCreates a new Person.
Action
Find CompanyFinds an existing company.
Action
Find LeadFinds an existing lead by a particular field. Defaults to searching open leads, falls back to all leads.
Action
Find PersonFinds an existing person.
Action
Find UserFinds an existing User.
Action
Log ActivityCreates and logs a new Activity.
Action
Update CompanyUpdates an existing Company.
Action
Update LeadUpdates an existing Lead.
Action
Update Lead OutcomeUpdates a Lead Outcome.
Action
Update PersonUpdates an existing Person.
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.
Each app on its own
Reviews