Mureka icon

Mureka

Interacts with the Mureka API to generate music via AI.

Actions9

Text To Speech → Create Podcast

AI-generated

Overview

The node integrates with the Mureka API to generate AI-driven audio content, specifically focusing on transforming scripted conversations into podcast-style audio. The "Create Podcast" operation under the "Text To Speech" resource takes an array of conversation snippets, each with text and a specified voice, and produces a ready-to-publish podcast audio output. This is useful for automating podcast production from scripts involving multiple speakers or characters.

Practical examples include:

  • Creating multi-voice podcasts from written dialogues.
  • Generating audio dramas or interviews with distinct voices.
  • Automating narration for storytelling or educational content with different speakers.

Properties

Name Meaning
Conversations A JSON array representing the conversation script. Each element includes text (the spoken content) and voice (the voice to use for that segment). Example: [{"text": "Hello, my name is Luna.", "voice":"Luna"}, ...]

Output

The node outputs a JSON array containing the response from the Mureka API after processing the podcast creation request. The exact structure depends on the API but typically includes information such as URLs to the generated audio files, status, and metadata about the podcast.

If the API returns binary data (e.g., audio files), it would be represented in the output accordingly, but this node primarily returns JSON metadata referencing the generated audio.

Dependencies

  • Requires an API key credential for authenticating requests to the Mureka API.
  • Network access to https://api.mureka.ai endpoints.
  • Proper configuration of the API authentication within n8n credentials.

Troubleshooting

  • Invalid Conversations Format: Ensure the "Conversations" property is a valid JSON array with objects containing both text and voice fields.
  • API Authentication Errors: Verify that the API key credential is correctly set up and has necessary permissions.
  • Empty or Missing Conversations: The node requires at least one conversation entry; an empty array will likely cause errors.
  • Unexpected API Responses: If the API returns errors, check network connectivity and API usage limits.
  • Voice Names: Use only supported voice names as defined by the Mureka API to avoid generation failures.

Links and References

Discussion