Integration
Connect Pipedrive to Simpleen Translation
When something happens in Pipedrive, 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 Pipedrive 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 Pipedrive and Simpleen Translation
Triggers and actions 5 triggers ยท 37 actions
Trigger
New ActivityTriggers when a new activity is created (polling).
Trigger
New DealTriggers when a new deal is created (polling).
Trigger
New OrganizationTriggers when a new organization is added (polling).
Trigger
New PersonTriggers when a new person (contact) is added (polling).
Trigger
New Person (with Custom Fields and Labels)Triggered when a new person (contact) is added. Includes custom fields and labels.
Action
Create ActivityCreates a new activity (call, meeting, task, etc.).
Action
Create DealAdds a new deal to Pipedrive. Returns the created deal.
Action
Create LeadCreates a new lead. Returns the created lead.
Action
Create NoteAdds a new note to a deal, person, or organization.
Action
Create OrganizationAdds a new organization. Returns the created organization.
Action
Create PersonAdds a new person (contact). Returns the created person.
Action
Delete ActivityMarks an activity as deleted.
Action
Delete DealMarks a deal as deleted.
Action
Delete OrganizationMarks an organization as deleted.
Action
Delete PersonMarks a person as deleted.
Action
Get DealReturns the deal with the given ID.
Action
Get OrganizationReturns the organization with the given ID.
Action
Get PersonReturns the person with the given ID.
Action
Get related deals for personReturns deals having the specified status that are related to the specified person.
Action
Get stage ID by stage nameReturns the stage id if the stage name exists.
Action
Merge organizationsMerges two organization accounts. Info from the organization record to discard is merged into the organization record to keep.
Action
Merge personsMerges two person accounts. Info from the person record to discard is merged into the person record to keep.
Action
Search DealsSearches deals by term. Returns matching deals.
Action
Search OrganizationsSearches organizations by term. Returns matching organizations.
Action
Search PersonsSearches persons by term (name, email, phone). Returns matching persons.
Action
Update ActivityUpdates an existing activity by ID.
Action
Update DealUpdates an existing deal by ID.
Action
Update OrganizationUpdates an existing organization by ID.
Action
Update PersonUpdates an existing person by ID.
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