Integration
Connect noCRM.io to Simpleen Translation
When something happens in noCRM.io, 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 noCRM.io 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 noCRM.io and Simpleen Translation
Triggers and actions 8 triggers ยท 29 actions
Trigger
Lead Status ChangedTriggers when a specific status of the lead is changed.
Trigger
New Client FolderTriggers when a client folder is created.
Trigger
New Deleted LeadTriggers when a lead is deleted. This trigger only works for Expert edition and above .
Trigger
New LeadTriggers when a lead is created.
Trigger
New Lead AssignedTriggers when a lead is assigned or re-assigned to someone. This trigger only works for Expert edition and above .
Trigger
New Lead CommentTriggers when a lead is comment on. This trigger only works for Expert edition and above .
Trigger
New Lead Content or Title ChangedTriggers when the content or the title of a lead is updated. This trigger only works for Expert edition and above .
Trigger
New ProspectTriggers when a prospect is created in any prospecting list or in a specific one. This trigger only works for Expert edition and above .
Action
Add AttachmentAdd an attachment to a lead
Action
Add CommentCreate a comment on a specific lead based on the parameters given. This action only works for Expert edition and above .
Action
Add TagsCreate a new tag on a specific lead based on the parameters given. This action only works for Expert edition and above .
Action
Assign LeadAssign the lead to a user
Action
Call Simplified APICall our simplified API to interact with your data
Action
Change Lead's TitleChange the title of a lead
Action
Change StatusChange the status of a lead to Standby, Won, Cancelled or Lost
Action
Change StepChange the step of a lead
Action
Create LeadCreates a new lead.
Action
Create ProspectCreate a prospect on a specific prospecting list based on the data given. This action only works for Expert edition and above .
Action
Delete LeadMoves a lead to the trash.
Action
Find LeadFinds a lead from an email address.
Action
Get LeadLook up one lead by its id and return its full details, including its status, reminder, amount, owner and your account's own custom fields.
Action
Log an ActivityLog an activity on a specific lead based on the parameters given. This action only works for Expert edition and above .
Action
Set Amount and ProbabilitySet the amount and the probability of a lead
Action
Set the Estimated Closing DateSet the estimated closing date on a lead
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.