Integration
Connect CloudConvert and Particle
When Job Failed fires in CloudConvert, your agent runs Publish an event in Particle, or New device event (instant) in Particle 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 Particle 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 CloudConvert and Particle can do together
From CloudConvert to Particle
When Job Failed in CloudConvert
then Publish an event in Particle
When Job Finished in CloudConvert
then Execute a logic function in Particle
From Particle to CloudConvert
When New device event (instant) in Particle
then Convert a File in CloudConvert
When New device event (instant) in Particle
then Get file metadata in 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 Particle
Triggers and actions 3 triggers · 9 actions
Trigger
Job FailedTriggers when a job failed.
Trigger
Job FinishedTriggers when a job finished.
Action
Capture a WebsiteCreates job to capture a website as PDF or create a website screenshot as JPG or PNG.
Action
Convert a FileCreates job to convert a file.
Action
Get file metadataExtract metadata (e.g. page count, dimensions, duration) from a file (metadata operation task).
Action
Get jobLook up the status and results of a conversion job by ID.
Trigger
New device event (instant)Fires when a matching device event is published, delivered via a Particle webhook integration.
Action
Execute a logic functionRun a configured Particle Logic function and return its result.
Action
Get ledger instanceRetrieve the current data for a ledger instance (shared cloud/device key-value state).
Action
List devicesList all devices in your account or product fleet.
Action
Publish an eventPublish a custom event to the device cloud so other devices or integrations can subscribe to it.
Action
Set ledger instance dataUpdate the data stored in a ledger instance.
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 CloudConvert
CloudConvert to Earnings FeedReal-time SEC filings, insider trades, and institutional holdings
CloudConvert to Google GeminiGoogle AI Studio is a fast, easy way to start prototyping generative AI ideas using Google's Gemini model.
CloudConvert to Open Government, Queensland GovernmentQueensland Government Open Data. Public open-data portal — search dataset catalogs and retrieve published...
CloudConvert to Studio GhibliThe Studio Ghibli API is a public catalogue of the people, places and things from the Studio Ghibli film...
CloudConvert to TrengoTrengo is a team collaboration tool to manage conversations from channels such as web chat, email and...
CloudConvert to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
More into Particle
NetHunt CRM to ParticleNetHunt CRM ties to Gmail and other Google Workspace apps you work in, automates data flow, and makes...
HubSpot to ParticleHubSpot is your all-in-one stop for all of your marketing software needs.
Gmail to ParticleGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to ParticleGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to ParticleGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Mailchimp to ParticleMailchimp marketing automation and email platform.
Questions
CloudConvert and Particle, answered
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 Particle when something happens in CloudConvert?
Any of Particle's 5 actions, including Execute a logic function, Get ledger instance, List devices and Publish an event. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Particle to CloudConvert?
Yes. When something happens in Particle, your agent can act in CloudConvert too. This page covers both directions: Particle's triggers and CloudConvert's actions are listed here as well.
Do I have to build a connector for CloudConvert or Particle?
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 Particle 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.