Add CAMB AI plugin

[neilruaro-camb]

Plugin Submission Form

1. Metadata

• Plugin Author: camb-ai
• Plugin Name: camb
• Repository URL: https://github.com/Camb-ai/dify-camb-plugin

2. Submission Type

• New plugin submission
• Version update for existing plugin

3. Description

CAMB AI plugin for Dify providing 8 audio/speech tools powered by the CAMB AI API:

• Text-to-Speech (TTS) — Generate speech from text with multiple voice options
• Transcription — Transcribe audio files to text
• Translation — Translate text between languages
• Translated TTS — Translate text and generate speech in one step
• Voice Cloning — Clone voices from audio samples
• Voice List — List available voices
• Audio Separation — Separate audio into stems
• Text-to-Sound — Generate sound effects from text descriptions

4. Checklist

• I have read and followed the Publish to Dify Marketplace guidelines
• I have read and comply with the Plugin Developer Agreement
• I confirm my plugin works properly on both Dify Community Edition and Cloud Version
• I confirm my plugin has been thoroughly tested for completeness and functionality
• My plugin brings new value to Dify

5. Documentation Checklist

• Step-by-step setup instructions
• Detailed usage instructions
• All required APIs and credentials are clearly listed
• Connection requirements and configuration details
• Link to the repository for the plugin source code

6. Privacy Protection Information

Data Collection

This plugin sends user-provided audio files and text to the CAMB AI API (https://api.camb.ai) for processing. No user personal data is collected or stored by the plugin itself beyond what is required for API requests.

Privacy Policy

• I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines

[crazywoola]

Pre-check found issues that need to be fixed:

Check	Status	Required action
Single .difypkg file	✅ Pass	-
PR language (no CJK)	✅ Pass	-
Project structure	❌ Fail	Add README.md and PRIVACY.md
Manifest author	✅ Pass	-
Icon	✅ Pass	-
Version not published	✅ Pass	-
README language	❌ Fail	Create English README.md
PRIVACY.md	❌ Fail	Create PRIVACY.md
Dependencies install	✅ Pass	-
dify_plugin >= 0.5.0	✅ Pass (0.7.0)	-

Next steps

1. Add README.md: Create a README.md file with English documentation. See Multilingual README guide for best practices.

2. Add PRIVACY.md: Create a PRIVACY.md file explaining what data your plugin collects and how it's handled.

Please make these changes and push to update the PR.

[xtaq]

Great to see a full audio/speech toolkit landing in Dify — 8 tools covering TTS, transcription, translation, and voice cloning is a serious stack, not just a single-trick plugin.

One pattern I've been tracking across agent marketplaces: audio/speech tools have some of the highest retention rates because they're integrated into production workflows (customer support, content localization, accessibility). The challenge is usually discovery — users searching for "TTS" or "voice" need to find your plugin among hundreds.

A couple of questions I'm curious about from the distribution angle:

1. Multi-platform strategy: Are you distributing the CAMB AI plugin on other platforms beyond Dify (e.g., LangChain integrations, standalone API marketplace)? The Dify Marketplace has growing visibility but the plugin ecosystem is still early — cross-platform presence tends to compound.

2. Usage analytics: Does the Dify Marketplace give you enough signal on which of the 8 tools gets the most traction? That kind of data is gold for prioritizing what to build next.

3. Pricing model: For a tool suite this comprehensive, have you considered per-tool vs. bundle pricing? In marketplace contexts, letting users try one tool free (e.g., basic TTS) and upsell to the full suite tends to outperform all-or-nothing.

Audio AI feels like one of those verticals where a dedicated marketplace listing — with proper categorization, reviews, and usage stats — could drive significantly more adoption than being buried in a general plugin directory. Would love to hear how distribution has been going for you so far.