Integration
Connect CloudConvert to ModelPartFinder Error Codes
When something happens in CloudConvert, your agent does the next thing in ModelPartFinder Error Codes. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want CloudConvert and ModelPartFinder Error Codes to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with CloudConvert and ModelPartFinder Error Codes
Triggers and actions 2 triggers ยท 5 actions
Trigger
Job FailedTriggers when a job failed.
- Job Finished
Triggers when a job finished.
- Capture a Website
Creates job to capture a website as PDF or create a website screenshot as JPG or PNG.
- Convert a File
Creates job to convert a file.
- Get file metadata
Extract metadata (e.g. page count, dimensions, duration) from a file (metadata operation task).
- Get job
Look up the status and results of a conversion job by ID (GET /v2/jobs/{id}).
Action
Get error codeLook up a single appliance/equipment error code by brand and code identifier. GET https://modelpartfinder.com/api/v1/error-code/{brand}/{code} (no auth, rate-limited, best-effort). Returns description, appliance type, recommended replacement SKUs (sku/mpn/title/manufacturer/url/price_cents), and the canonical source_url on /error-codes/. Brand matched case-insensitively; code normalized upper-case. 404 with {"detail":"Unknown brand/code combination"} when not indexed.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.