Integration

Connect lemlist to Simpleen Translation

When something happens in lemlist, 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.

lemlist1 triggerlemlist8 actionsSimpleen Translation13 actions

Browse all apps

Build it

What do you want lemlist 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 Code

Everything your agent can do with lemlist and Simpleen Translation

Triggers and actions 1 trigger · 21 actions

Trigger
New Activity
Triggers when an activity has ocurred. It can be an email has been sent, replied to, bounced, or unsubscribed from or v3 new activity like a LinkedIn profile have been visited or a phone call just ended.
Action
Add Recipient to Unsubscribe List
Add a recipient to the unsubscribe list.
Action
Mark a Lead From All Campaigns as Interested
Mark a Lead From All Campaigns as Interested.
Action
Mark a Lead From One Campaign as Interested
Mark a Lead From One Campaign as Interested.
Action
Remove Lead From Campaign
Remove a Lead from a campaign.
Action
Remove Lead From Unsubscribe
Remove a Lead from unsubscribe.
Action
Resume Lead From All or Specific Campaigns
Resume Lead From All or Specific Campaigns.
Action
Search Lead
Search a lead.
Action
Update Lead From Campaign
Update Lead From Campaign.
Action
Add glossary
Create a new glossary of word entries/ignored terms for translation. POST /glossaries.
Action
Add segment
Create a new translation segment (source entry + translated entry) tied to a file. POST /segments.
Action
Create Translation
Translates content to selected target language
Action
Get file
Get a specific localization file by id, including its segments and languages. GET /files/{id}.
Action
Get glossary
Get a specific glossary by id, including its entries and ignored words. GET /glossaries/{id}.
Action
Get segment
Get a specific translation segment by id. GET /segments/{id}.
Action
List files
List the localization files known to the account. GET /files.
Action
List glossaries
List the user's glossaries (word lists of ignored terms + custom translations). GET /glossaries.
Action
List languages
List all supported languages (DeepL/Google Translate backed) with source/target flags. GET /languages.
Action
List segments
List translatable segments (source/translated entry pairs) across the user's files. GET /segments.
Action
Run translator
Translate text using a saved, preconfigured Translator (reusable source/target language + format + glossary setup). POST /translators/{id}/translate.
Action
Update glossary
Update an existing glossary's name, entries, or ignored words. PUT /glossaries/{id}.
Action
Update segment
Post-edit an existing translation segment's entry to fix/correct future translation usage. PUT /segments/{id}.

Each app on its own

The other way round: Simpleen Translation to lemlist