Convertapi integration

Quick start

Call Convertapi from your generated app's worker code via the OverSkill composio client. The toolkit slug below maps to Convertapi's public Composio identifier — your app references it by name and OverSkill handles the OAuth round-trip.

// In your generated app's worker handler:
const composio = composioClient(env);

const result = await composio.execute(
  "CONVERTAPI_ACTION_NAME",
  { /* action parameters — see Actions section below */ }
);

return new Response(JSON.stringify(result), {
  headers: { "Content-Type": "application/json" }
});

Replace ACTION_NAME with one of the slugs listed in the Actions section below. The composio client handles auth + rate limits automatically — no API key is exposed to user code.

Setup

End-users supply their own Convertapi API key. OverSkill provides a pre-built connection form via the integration card — your app can call the composio client immediately once the user has connected.

Available actions

17 actions exposed via the Convertapi integration. Each maps to a callable slug — pass it to composio.execute(...) in your worker code.

• CONVERTAPI_ASYNC_CONVERT
• CONVERTAPI_ASYNC_DELETE_JOB
• CONVERTAPI_CHECK_CONVERSION_SUPPORT
• CONVERTAPI_CONVERT_DELETE_UPLOADED_FILE
• CONVERTAPI_CONVERT_GET_SUPPORTED_INPUT_FORMATS_FOR_OUTPUT
• CONVERTAPI_CONVERT_PDF_TO_DOCX
• CONVERTAPI_CONVERT_PDF_TO_JPG_AND_STORE
• CONVERTAPI_CONVERT_UPLOAD_FILE_FROM_URL
• CONVERTAPI_DOWNLOAD_FILE
• CONVERTAPI_DOWNLOAD_UPLOADED_FILE
• CONVERTAPI_GET_CONVERTER_SPEC
• CONVERTAPI_GET_FILE_INFO