Integration
Connect Trengo to OpenRegister
When something happens in Trengo, your agent does the next thing in OpenRegister. 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 Trengo and OpenRegister 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 Trengo can start in OpenRegister
When New Internal Note in Trengo
then Find Company by Name in OpenRegister
When New Outbound Message in Trengo
then Find Company by URL in OpenRegister
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 Trengo and OpenRegister
Triggers and actions 3 triggers · 28 actions
Trigger
New Internal NoteFires when an internal note is added to a Trengo ticket.
Trigger
New Outbound MessageTriggers when an outbound message is created.
Trigger
Ticket Label AddedTriggers when a label is added to a conversation.
Action
Add internal note to ticketAdds an internal note (visible only to agents) to a Trengo ticket.
Action
Add ticketCreate a new support ticket.
Action
Add ticket labelAttaches an existing label to a Trengo ticket.
Action
Create a ContactCreates 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.
Action
Create webhookSubscribes a URL to one Trengo webhook event type. Used by Trengo instant triggers to register their delivery URL on activation.
Action
Delete contactDelete a contact by id.
Action
Delete ticketDelete a ticket by id.
Action
Find a ContactReturns the Trengo contacts that match the search term.
Action
Get contactRetrieve a single Trengo contact by its id.
Action
Get webhookFetches 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.
Action
List contactsList all contacts.
Action
List labelsLists the ticket labels defined in the Trengo account (first page).
Action
List ticketsReturns all tickets the connected user is authorized to see, optionally filtered by status, contact, users, channels, labels, last message type or update time.
Action
Send a MessageSends a reply message on an existing Trengo ticket, over the ticket's own channel.
Action
Update contactUpdate an existing contact by id.
Action
Find Company by NameReturns German companies whose current or historical registered name matches the specified name.
Action
Find Company by URLFinds the German company behind a website URL and returns its company ID plus the email, phone and VAT ID found on the site.
Action
Find Insolvency ProceedingsReturns German insolvency proceedings (companies and natural persons) that match a free-text search and/or structured filters.
Action
Find People by NameReturns people from the German commercial register whose name matches the search text, optionally narrowed by city, date of birth or active status.
Action
Get Company Contact InformationRetrieve contact information for a German company: email, phone, VAT ID and the source web page.
Action
Get Company DetailsReturns the full register record of a German company by its OpenRegister ID.
Action
Get Company Historical OwnersRetrieves the full ownership history of a German company (GmbH only) across every shareholder list it has filed.
Action
Get Company HoldingsRetrieves the list of companies that a German company owns or has stakes in, including relation type and share amounts. Costs 10 OpenRegister credits per call.
Action
Get Company OwnersRetrieves the shareholders and owners of a German company, with their ownership percentages, nominal shares and register roles.
Action
Get Company UbosRetrieves the Ultimate Beneficial Owners (natural persons who ultimately own or control the company) of a German company, calculated across the full ownership chain. Costs 25 OpenRegister credits per call.
Action
Get Insolvency ProceedingRetrieve the full record of a single German insolvency proceeding, including its status, debtor, administrator, deadlines, distribution figures and complete event history.
Action
Get Person DetailsRetrieve detailed information about a person listed in the German commercial register: name, date of birth, age, city, and their current and past management positions across companies.
Action
Get Person HoldingsRetrieve the company holdings (ownership stakes) associated with a specific person by person 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 Trengo
Trengo to ZoomZoom unifies cloud video conferencing, simple online meetings, group messaging, and a software-based...
Trengo to TwilioCloud communications platform for sending SMS/MMS messages, making and managing voice calls, and looking up...
Trengo to TypeformBuild and publish online forms, surveys, and quizzes with Typeform.
Trengo to WebflowWebflow is a professional website builder and CMS for designing, building, and launching responsive...
Trengo to WixThe Wix website builder gives businesses of any size the tools to create, manage and grow a fully integrated...
Trengo to LinkedInLinkedIn is a professional networking platform enabling job seekers, companies, and thought leaders to...
More into OpenRegister
HubSpot to OpenRegisterHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to OpenRegisterSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to OpenRegisterSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to OpenRegisterGoogle Sheets
Gmail to OpenRegisterGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to OpenRegisterGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Trengo and OpenRegister, answered
What can start an automation from Trengo?
Any of Trengo's 3 triggers in the catalog, including New Internal Note, New Outbound Message and Ticket Label Added. Describe the moment in plain language and your agent picks the right one.
What can your agent do in OpenRegister when something happens in Trengo?
Any of OpenRegister's 13 actions, including Find Company by Name, Find Company by URL, Find Insolvency Proceedings and Find People by Name. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from OpenRegister to Trengo?
OpenRegister has no triggers in the catalog today, so automations start in Trengo. If you need the other direction, ask: your agent reads OpenRegister's API documentation and adds it.
Do I have to build a connector for Trengo or OpenRegister?
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.