Connect only the destinations your workflow actually needs.
EchoVerse AI connects creation, publishing, advertising and measurement through authorized accounts. A provider must be enabled and properly authorized before live delivery or synchronization can occur.
The customer application is the source of truth for which account types and actions are currently enabled in your workspace. Public pages describe the connection model without promising that every provider feature is enabled for every account.
EchoVerse AI Platform
Video & Channel Destinations
Advertising Accounts
Business & Content Sources
A successful connection needs more than a button click.
Before troubleshooting publishing or synchronization, verify the provider account, permissions, selected destination and item state.
Answers before you need support.
Open a question to see the answer. If the answer depends on your plan, permissions or a connected provider, the app remains the source of truth for what is enabled in your workspace.
Does connecting a provider give EchoVerse AI access to everything in that account?
No. Access is limited by the authorization scopes, account permissions and capabilities used by the enabled integration.
Can I choose which YouTube channel receives content?
When eligible channels are available through the authorized account, EchoVerse AI can map an EchoVerse channel to the selected YouTube channel so content is routed intentionally.
Why can a connection show as authorized but publishing still fail?
Authorization is only one requirement. The content must also be in a publishable state, required metadata must be valid, the destination mapping must exist, and the provider can still reject a request for its own rules or limits.
Can I disconnect an account later?
Yes. You can remove or revoke a connection when you no longer want EchoVerse AI to use it. Provider-side revocation may also be available from the provider account.
Do all providers support the same actions?
No. Publishing, scheduling, reporting, account structure and metadata requirements differ by provider. The app should only show actions supported by the active connection and workflow.
Most questions can be resolved without opening a support request.
Use the Help Center for troubleshooting, Documentation for workflow guidance, Examples to understand output formats, and Pricing for current plan limits and billing information.
