Integration

Connect CloudConvert and Trengo

When Job Failed fires in CloudConvert, your agent runs Add ticket label in Trengo, or New Internal Note in Trengo to Convert a File in CloudConvert. 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 CloudConvert and Trengo to do together?

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

Examples

Pick one to fill the box, then change anything: the steps, the wording, even the apps. Go as long as you like.

Connect your AI client

Give your AI client this address.

https://mcp.apiant.ai

One 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.ai

Start 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)

CloudConvert turns files into the format you need, and Trengo is where your team talks to customers. Joining them means a file that arrives or is requested in a Trengo conversation can be converted, captured or measured in CloudConvert, with the result posted back as an internal note, a label or a reply on the same ticket.

Example flows

What CloudConvert and Trengo can do together

From CloudConvert to Trengo

From Trengo to CloudConvert

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 CloudConvert and Trengo

Triggers and actions 5 triggers · 19 actions

Each app on its own

Reviews

What our customers say

More from CloudConvert

More into Trengo

Questions

CloudConvert and Trengo, answered

Can the converted file be sent back to the customer in the same conversation?

Yes. A finished CloudConvert job can trigger Send a Message on the Trengo ticket, so the reply goes out over that ticket's own channel. You can also add an internal note first so agents see the job result before anything leaves the inbox.

What happens when a conversion does not go through?

CloudConvert has a Job Failed trigger, so you can attach a label to the Trengo ticket or add an internal note for the agent handling it. The agent building this tests every scenario, including the failed job, before it runs on live conversations.

What can start an automation from CloudConvert?

Any of CloudConvert's 2 triggers in the catalog, including Job Failed and Job Finished. Describe the moment in plain language and your agent picks the right one.

What can your agent do in Trengo when something happens in CloudConvert?

Any of Trengo's 15 actions, including Add ticket label, Send a Message, Create a Contact and Create webhook. Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from Trengo to CloudConvert?

Yes. When something happens in Trengo, your agent can act in CloudConvert too. This page covers both directions: Trengo's triggers and CloudConvert's actions are listed here as well.

Do I have to build a connector for CloudConvert 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 CloudConvert 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.