Use the CloudConvert CLI from KosmoKrator to call CloudConvert tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.
CloudConvert can be configured headlessly with `kosmokrator integrations:configure cloudconvert`.
# Install KosmoKrator first if it is not available on PATH.curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash# Configure and verify this integration.kosmokrator integrations:configure cloudconvert --set api_key="$CLOUDCONVERT_API_KEY" --enable --read allow --write ask --jsonkosmokrator integrations:doctor cloudconvert --jsonkosmokrator integrations:status --json
Credentials
Authentication type: API keyapi_key. Configure credentials once, then use the same stored profile from
scripts, coding CLIs, Lua code mode, and the MCP gateway.
Key
Env var
Type
Required
Label
api_key
CLOUDCONVERT_API_KEY
Secret secret
yes
API Key
url
CLOUDCONVERT_URL
URL url
no
API Base URL
Call CloudConvert Headlessly
Use the generic call form when another coding CLI or script needs a stable universal interface.
Every function below can be called headlessly. The generic form is stable across all integrations;
the provider shortcut is shorter but specific to CloudConvert.
cloudconvert.cloudconvert_create_job
Write write
Create a new CloudConvert job. A job groups one or more tasks (import, convert, export) into a single workflow. Pass a tasks array to define the conversion pipeline.
Create a standalone CloudConvert task. Specify an operation (e.g., import/url, convert, export/url, capture-website, merge, optimize, thumbnail) and the operation-specific payload.
Use these parameter tables when building CLI payloads without calling integrations:schema first.
cloudconvert.cloudconvert_create_job
Create a new CloudConvert job. A job groups one or more tasks (import, convert, export) into a single workflow. Pass a tasks array to define the conversion pipeline.
Array of task definitions. Each task is an object with "operation" (e.g., "import/url", "convert", "export/url"), optional "name", optional "input" (name of a previous task to chain from), and operation-specific parameters. Example: [{"operation": "import/url", "url": "https://example.com/file.pdf", "filename": "file.pdf"}, {"operation": "convert", "input": "import", "output_format": "png"}].
tag
string
no
Optional tag to identify and filter the job later.
webhook_url
string
no
Optional webhook URL called when the job finishes.
cloudconvert.cloudconvert_get_job
Get details and status of a CloudConvert job by ID, including all associated tasks and their results.
Filter by status: waiting, processing, finished, error.
tag
string
no
Filter by job tag.
cloudconvert.cloudconvert_create_task
Create a standalone CloudConvert task. Specify an operation (e.g., import/url, convert, export/url, capture-website, merge, optimize, thumbnail) and the operation-specific payload.
The task operation. Common operations: "import/url", "import/upload", "import/base64", "convert", "export/url", "export/aws-s3", "capture-website", "merge", "optimize", "thumbnail", "metadata", "archive".
payload
array
no
Operation-specific parameters. For "convert": output_format, input_format, options (e.g., quality, density). For "import/url": url, filename. For "export/url": no extra payload needed.
name
string
no
Optional name for the task (used to reference as input for subsequent tasks in a job).
input
string
no
Name of a previous task whose output this task should use as input.
cloudconvert.cloudconvert_get_task
Get details and status of a CloudConvert task by ID, including the result payload with download URLs for completed conversions.
Headless calls still follow the integration read/write permission policy. Configure read/write defaults
with integrations:configure. Add --force only for trusted automation that should bypass that policy.