Integration
Connect Copper to Simpleen Translation
When something happens in Copper, 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 Copper 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 Copper and Simpleen Translation
Triggers and actions 17 triggers ยท 35 actions
Trigger
New ActivityTriggers when a new activity is created.
Trigger
New CompanyTriggers when a new Company is created in Copper.
Trigger
New LeadTriggers when a Lead is created in Copper.
Trigger
New OpportunityTriggers when an Opportunity is created in Copper.
Trigger
New PersonTriggers when a new Person is created in Copper.
Trigger
New ProjectTriggers when a new Project is created in Copper.
Trigger
New TaskTriggers when a new Task is created in Copper.
Trigger
Updated CompanyTriggers when a Person's Company is changed.
Trigger
Updated Contact TypeTriggers when a Person's Contact Type is changed.
Trigger
Updated LeadTriggers when a Lead is changed.
Trigger
Updated Lead StatusTriggers when a Lead's status is changed.
Trigger
Updated OpportunityTriggers when an Opportunity is changed.
Trigger
Updated Opportunity StageTriggers when an Opportunity's stage is changed.
Trigger
Updated Opportunity StatusTriggers when an Opportunity's status is changed.
Trigger
Updated PersonTriggers when a Person is changed.
Trigger
Updated ProjectTriggers when a Project is changed.
Trigger
Updated TaskTriggers when a Task is changed.
Action
Associate to ProjectThis Action allows you to relate an existing Project to and existing CRM object; both objects have to exist before you run this Action. This Action expects two ID's for input: the ID of the CRM record you want to relate to and the Project ID you want to relate it with. This Action was designed to be used in multi-step Zaps, where you already have a Project ID and an related record ID (e.g. a Person) from previous steps.
Action
Create ActivityLogs a new Activity on a Person, Company, Opportunity, or Lead.
Action
Create CompanyCreates a new Company.
Action
Create LeadCreates a new Lead.
Action
Create OpportunityCreates a new Opportunity.
Action
Create PersonCreates a new Person.
Action
Create ProjectCreates a new Project.
Action
Create TaskCreates a new Task.
Action
Create/Update CompanyCreates or Updates a Company depending on the match criteria.
Action
Create/Update LeadCreates or Updates a Lead depending on the match criteria.
Action
Create/Update OpportunityCreates or Updates an Opportunity based off of a match criteria.
Action
Create/Update PersonCreates or Updates a Person depending on the match criteria.
Action
Create/Update ProjectCreates or Updates a Project depending on the match criteria.
Action
Search for a CompanySearches for an existing company in Copper.
Action
Search for an ActivitySearches for an existing activity in Copper.
Action
Search for a OpportunitySearches for an existing opportunity in Copper.
Action
Search for a PersonSearches for an existing person in Copper.
Action
Search for a ProjectSearches for an existing project in Copper.
Action
Update CompanyUpdates a Company depending on the match criteria.
Action
Update OpportunityUpdates an Opportunity based off of a match criteria.
Action
Update PersonUpdates a Person depending on the match criteria.
Action
Update ProjectUpdates a Project depending on the match criteria.
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.