CloudConvert node not available in n8n Cloud – installation of community package is forbidden

<Hello n8n team,
I’m facing a blocking issue related to CloudConvert in n8n Cloud.
The problem:

  • The CloudConvert node is not available in n8n Cloud.
  • Installing the community package @cloudconvert/n8n-nodes-cloudconvert is forbidden.
  • I receive the error: “installation of unverified community packages is forbidden”.
  • Existing workflows depending on CloudConvert are now broken.
    Context:
  • I’m using n8n Cloud (not self-hosted).
  • My workflow depends on file conversion (PDF → images / text).
  • I tried using HTTP Request with CloudConvert API as a workaround, but it’s unclear if this is the official or recommended approach.
    Questions:
  1. Was the CloudConvert node officially removed from n8n Cloud?
  2. What is the official recommended alternative for file conversion in n8n Cloud?
  3. Is HTTP Request + external API the correct long-term solution?
  4. Are there plans to provide an official built-in conversion node?
    This issue is blocking a production workflow.
    Thank you for your support.
    – Hey! The fastest way to find solutions is by using the :magnifying_glass_tilted_right: search function at the upper right.
    If your question hasn’t been asked before, please follow the template below. Skip the questions that are not relevant to you. →

Describe the problem/error/question

What is the error message (if any)? Error installing new package: installation of unverified community packages is forbidden

Please share your workflow Workflow cannot be shared because the CloudConvert node is not available in n8n Cloud.)

Share the output returned by the last node

Information on your n8n setu

n8n version: n8n Cloud (latest)
Database: n8n Cloud (managed)
n8n EXECUTIONS_PROCESS setting: default
Running n8n via: n8n Cloud
Operating system: macOS

The CloudConvert node is unverified, not removed - n8n Cloud restricts installations to verified community nodes only. HTTP Request + CloudConvert API is possible long-term solution.

Alternative for any document to text: Ainoflow Convert, handles OCR/conversion via HTTP request. Sample available: Track expenses automatically with Telegram Bot using GPT-4o, OCR and voice recognition | n8n workflow template

1 Like

Thanks for the clarification, this helps a lot.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.