Integration
Connect Productboard and Trengo
When something happens in Productboard or Trengo, your agent does the next thing in the other. Describe it and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Productboard and Trengo to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Productboard and Trengo can do together
From Productboard to Trengo
When New Feature in Productboard
then Add internal note to ticket in Trengo
From Trengo to Productboard
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Productboard and Trengo
Triggers and actions 7 triggers · 27 actions
- New Feature
Triggered when a new feature is created in Productboard.
- New Note
Triggered when a new note (a piece of customer feedback) is created in Productboard.
- Updated Feature
Triggered when a feature is created or changed in Productboard.
- Updated Note
Triggered when a note (a piece of customer feedback) is created or changed in Productboard.
- Create Company
Creates 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.
- Create Feature
Creates 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.
- Create Note
Creates 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.
- Find Note
Looks 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.
- Get Company
Returns one company from Productboard by its ID, including its name, domain, description, owner and any custom fields set up in your workspace.
- Get Feature by ID
Returns one feature from Productboard by its ID, including its name, description, owner, status and any custom fields set up in your workspace.
- List Components
Returns the components in your Productboard workspace — the folders that features live under. Use a component's ID as the parent when creating a feature.
- List Members
Returns 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.
- List Note Relationships
Returns everything a Productboard note is linked to — the customer or company it came from and the features it has been connected to.
- List Products
Returns 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.
- List Releases
Returns the releases in your Productboard workspace — the buckets features are grouped into for delivery — with their status and dates.
- Update Note
Changes an existing note in Productboard. Only the values you fill in are sent, so anything left empty keeps its current value.
- New Internal Note
Fires when an internal note is added to a Trengo ticket.
- New Outbound Message
Triggers when an outbound message is created.
- Ticket Label Added
Triggers when a label is added to a conversation.
- Add internal note to ticket
Adds an internal note (visible only to agents) to a Trengo ticket.
- Add ticket
Create a new support ticket.
- Add ticket label
Attaches an existing label to a Trengo ticket.
- Create a Contact
Creates a contact on a Trengo channel. If a contact with the same identifier already exists on that channel, Trengo returns the existing contact instead of creating a duplicate.
- Create webhook
Subscribes a URL to one Trengo webhook event type. Used by Trengo instant triggers to register their delivery URL on activation.
- Delete contact
Delete a contact by id.
- Delete ticket
Delete a ticket by id.
- Find a Contact
Returns the Trengo contacts that match the search term.
- Get contact
Retrieve a single Trengo contact by its id.
- Get webhook
Fetches a webhook by ID, including the event it listens for, the address it sends to and its signing secret. An error occurs if the webhook is not found.
- List contacts
List all contacts.
- List labels
Lists the ticket labels defined in the Trengo account (first page).
- List tickets
Returns all tickets the connected user is authorized to see, optionally filtered by status, contact, users, channels, labels, last message type or update time.
- Send a Message
Sends a reply message on an existing Trengo ticket, over the ticket's own channel.
- Update contact
Update an existing contact by 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
What our customers say
More from Productboard
Productboard to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Productboard to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Productboard to Google SheetsGoogle Sheets
Productboard to StripeStripe is a payment processing platform for online businesses.
Productboard to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Productboard to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Trengo
HubSpot to TrengoHubSpot is your all-in-one stop for all of your marketing software needs.
Gmail to TrengoGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to TrengoGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Productboard and Trengo, answered
What can start an automation from Productboard?
Any of Productboard's 4 triggers in the catalog, including New Feature, New Note, Updated Feature and Updated Note. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Trengo when something happens in Productboard?
Any of Trengo's 15 actions, including Create a Contact, Create webhook, Send a Message and Update contact. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Trengo to Productboard?
Yes. When something happens in Trengo, your agent can act in Productboard too. This page covers both directions: Trengo's triggers and Productboard's actions are listed here as well.
Do I have to build a connector for Productboard or Trengo?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.