Integration
Connect Coworks and Trengo
When Contact Updated fires in Coworks, your agent runs Create a Contact in Trengo, or New Internal Note in Trengo to List CRM contacts and leads in Coworks. 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 Coworks 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)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 Coworks and Trengo can do together
From Coworks to Trengo
When Contact Updated in Coworks
then Create a Contact in Trengo
When CRM Entry Updated in Coworks
then Add internal note to ticket in Trengo
From Trengo to Coworks
When New Internal Note in Trengo
then List CRM contacts and leads in Coworks
When New Outbound Message in Trengo
then Get room occupancy in Coworks
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 Coworks and Trengo
Triggers and actions 13 triggers · 22 actions
Trigger
Contact UpdatedTriggers when a contact in your Coworks CRM is created or changed.
Trigger
CRM Entry UpdatedTriggers when a CRM contact or lead is added or changed in Coworks.
Trigger
Lead UpdatedTriggers when a lead in Coworks is created or changed, including changes to its status, custom fields, or any other returned detail.
Trigger
Member DeactivateTriggered when a member is deactivated and is no longer an active member.
Trigger
Member UpdatedTriggers when a member is added or any of a member's details change.
Trigger
New CheckinTriggered when a new check-in is recorded for a member, visitor or passport holder in your Coworks community.
Trigger
New ContactTriggered when a new contact is created in your Coworks CRM.
Trigger
New CRM EntryTriggered when a new CRM entry, either a contact or a lead, is created.
Trigger
New LeadTriggers when a new lead is created in the Coworks CRM.
Trigger
New MemberTriggered when a new member is created in your Coworks community.
Action
Get room occupancyReturns the rooms at a campus with their occupancy, optionally limited to one room type.
Action
List active membershipsReturns the community's paid memberships, optionally limited to one status. Free subscriptions are not included.
Action
List checkinsReturns check-ins for your Coworks community, optionally filtered by campus, check-in type, date range or person name.
Action
List CRM contacts and leadsReturns the contacts and leads in your Coworks CRM, optionally filtered by campus, type, lead status, source and date.
Action
List membersReturns the members of your Coworks community, optionally narrowed to specific teams or a campus, and optionally including inactive members.
Action
List roomsReturns the rooms at a campus, optionally narrowed to one room type.
Action
List teamsReturns the teams in your Coworks community, optionally narrowed by team, campus, or join date.
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.
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 Coworks
Coworks to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Coworks to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Coworks to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Coworks to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Coworks to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Coworks to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Trengo
OpenAI to TrengoOpenAI's platform for text generation (Responses + Chat Completions), image generation (gpt-image-1 /...
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.
Questions
Coworks and Trengo, answered
What can start an automation from Coworks?
Any of Coworks's 10 triggers in the catalog, including Contact Updated, CRM Entry Updated, Lead Updated and Member Updated. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Trengo when something happens in Coworks?
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 Coworks?
Yes. When something happens in Trengo, your agent can act in Coworks too. This page covers both directions: Trengo's triggers and Coworks's actions are listed here as well.
Do I have to build a connector for Coworks 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 Coworks 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.