JoggAI icon

JoggAI

Interact with the JoggAI API to create and manage AI videos
Join our community

Actions22

Overview

The "Get My Voices" operation under the "Voice" resource in this node allows users to retrieve a list of their custom AI voices from the JoggAI platform. This is useful for scenarios where you want to manage, preview, or select specific voice profiles for text-to-speech or other voice synthesis tasks within your automation workflows.

Practical examples include:

  • Fetching all available custom voices filtered by language to dynamically populate voice selection options.
  • Integrating with other nodes to generate audio content using a preferred voice.
  • Auditing or managing voice assets programmatically.

Properties

Name Meaning
Language Optional filter to narrow down the list of custom voices by spoken language. Options include: No Select (all languages), English, Filipino, French, German, Hindi, Indonesian, Italian, Japanese, Korean, Malay, Portuguese, Russian, Spanish, Thai, Vietnamese, Arabic, Greek, Turkish, Slovenian, Croatian, Romanian, Simplified Chinese, Bengali, Urdu, Hungarian, Traditional Chinese, Polish, Cantonese, Danish, Malayalam, Tamil, Telugu, Czech, Hebrew, Zulu, Swedish, Lithuanian, Dutch, Flemish, Norwegian, Finnish, Bulgarian, Latvian, Ukrainian, Mongolian, Persian, Odia, Assamese, Kannada, Tagalog, Amharic, Serbian, Slovak, Swahili

Output

The output JSON contains an array of voice objects representing the user's custom voices retrieved from the JoggAI API. Each object typically includes details such as voice ID, name, language, and other metadata describing the voice profile.

If the node supports binary data output (not explicitly shown here), it would likely relate to audio samples or voice files associated with the voices.

Dependencies

  • Requires an active connection to the JoggAI API via an API key credential configured in n8n.
  • The node depends on the JoggAI service being accessible and the user having appropriate permissions to access their custom voices.

Troubleshooting

  • Common issues:
    • Network connectivity problems preventing API calls.
    • Invalid or missing API authentication credentials.
    • Filtering by a language that has no associated voices returns an empty list.
  • Error messages:
    • Errors related to authentication failure indicate invalid or expired API keys; resolve by updating credentials.
    • API request failures may show messages about rate limits or service unavailability; retry after some time.
    • If the node throws errors about missing parameters, ensure the "Resource" is set to "Voice" and "Operation" to "Get My Voices".

Links and References

Discussion