Integration
Connect Productboard to Simpleen Translation
When something happens in Productboard, 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 Productboard 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 Productboard and Simpleen Translation
Triggers and actions 4 triggers · 25 actions
Trigger
New FeatureTriggered when a new feature is created in Productboard.
Trigger
New NoteTriggered when a new note (a piece of customer feedback) is created in Productboard.
Trigger
Updated FeatureTriggered when a feature is created or changed in Productboard.
Trigger
Updated NoteTriggered when a note (a piece of customer feedback) is created or changed in Productboard.
Action
Create CompanyCreates a company record in Productboard so customer feedback and insights can be attributed to it. Returns the new company's ID and a link to open it in Productboard.
Action
Create FeatureCreates a feature in Productboard under a product or component you choose. Optionally sets the description, owner and status. Returns the new feature's ID and a link to open it in Productboard.
Action
Create NoteCreates a note (a piece of customer feedback) in Productboard. Optionally attributes it to a company or customer, links it to a feature, and applies existing tags. Returns the new note's ID and a link to open it in Productboard.
Action
Find NoteLooks up a single note (customer feedback) in Productboard. Narrows the list by owner, created date and processed/archived state, then matches the text you give against the note's title and body. Returns the first match, or found=false.
Action
Get CompanyReturns one company from Productboard by its ID, including its name, domain, description, owner and any custom fields set up in your workspace.
Action
Get Feature by IDReturns one feature from Productboard by its ID, including its name, description, owner, status and any custom fields set up in your workspace.
Action
List ComponentsReturns the components in your Productboard workspace — the folders that features live under. Use a component's ID as the parent when creating a feature.
Action
List MembersReturns the people who have access to your Productboard workspace, with their email address and role. Optionally search by name or email and filter by role.
Action
List Note RelationshipsReturns everything a Productboard note is linked to — the customer or company it came from and the features it has been connected to.
Action
List ProductsReturns the products in your Productboard workspace — the top level of the product hierarchy. Use a product's ID as the parent when creating a feature or component.
Action
List ReleasesReturns the releases in your Productboard workspace — the buckets features are grouped into for delivery — with their status and dates.
Action
Update NoteChanges an existing note in Productboard. Only the values you fill in are sent, so anything left empty keeps its current value.
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.