Integration
Connect Lexopulus and Trengo
When Intake Form Published fires in Lexopulus, your agent runs Add internal note to ticket in Trengo, or New Internal Note in Trengo to Upload File in Lexopulus. Describe the whole flow 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 Lexopulus and Trengo to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 Lexopulus and Trengo can do together
From Lexopulus to Trengo
When Intake Form Published in Lexopulus
then Add internal note to ticket in Trengo
When Intake Form Published in Lexopulus
then Add ticket in Trengo
From Trengo to Lexopulus
When New Internal Note in Trengo
then Upload File in Lexopulus
When New Outbound Message in Trengo
then Submit Form in Lexopulus
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 Lexopulus and Trengo
Triggers and actions 4 triggers · 19 actions
Trigger
Intake Form PublishedTriggers when a new intake form is published in Lexopulus.
Action
Get Countries and StatesReturns the countries and states available for address fields in Lexopulus forms.
Action
Get Financial Info ValuesReturns the income sources, expense sources and source frequencies used by financial info fields.
Action
Get FormReturns one Lexopulus intake form with its categories and fields.
Action
List FormsReturns the published intake forms in your Lexopulus account, newest first.
Action
Submit FormSubmits a Lexopulus intake form with values for its categories and fields. Get Form returns the category and field IDs.
Action
Upload FileUploads a file so it can be attached to a form's file attachment field; returns the stored file's name and path.
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
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
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.
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 Lexopulus
Lexopulus to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Lexopulus to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Lexopulus to MailchimpMailchimp marketing automation and email platform.
Lexopulus to StripeStripe is a payment processing platform for online businesses.
Lexopulus to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Lexopulus to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
More into Trengo
CloudConvert to TrengoCloudConvert converts files between more than 200 supported formats: documents, image, spreadsheet...
elmah.io to TrengoCloud logging for .NET web applications using ELMAH.
Postman to TrengoPostman is a platform for building and testing APIs.
HubSpot to TrengoHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to TrengoSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to TrengoSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Questions
Lexopulus and Trengo, answered
What can start an automation from Lexopulus?
Any of Lexopulus's 1 trigger in the catalog, including Intake Form Published. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Trengo when something happens in Lexopulus?
Any of Trengo's 13 actions, including Create a Contact, Send a Message, Update contact and Add internal note to ticket. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Trengo to Lexopulus?
Yes. When something happens in Trengo, your agent can act in Lexopulus too. This page covers both directions: Trengo's triggers and Lexopulus's actions are listed here as well.
Do I have to build a connector for Lexopulus 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.
Can my AI client use Lexopulus and Trengo without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
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.