Mureka icon

Mureka

Interacts with the Mureka API to generate music via AI.

Actions9

Instrumental → Generate

AI-generated

Overview

This node integrates with the Mureka API to generate AI-based instrumental music. It supports generating new instrumentals based on a textual prompt describing style and theme or referencing an existing instrumental by ID. This is useful for musicians, producers, or content creators who want to quickly create background music or instrumentals tailored to specific moods or genres without manual composition.

Typical use cases include:

  • Creating custom instrumental tracks for songs or videos.
  • Experimenting with different musical styles by providing descriptive prompts.
  • Referencing and regenerating variations of existing instrumentals using their IDs.

For example, a user might input a prompt like "Embrace of Night / r&b, slow, passionate, male vocal" to generate a smooth R&B instrumental fitting that mood.

Properties

Name Meaning
Prompt Textual description of the instrumental style and theme to generate (e.g., genre, mood).
Model The AI model to use for generation. Options: Automatique, Mureka 6.
Instrumental ID Reference ID of an existing instrumental to regenerate or modify instead of using a prompt.

Output

The node outputs JSON data representing the result returned from the Mureka API for the instrumental generation request. This typically includes metadata about the generated instrumental such as its ID, status, URLs to audio files, and other relevant details.

No binary data output is produced directly by this node; it only returns JSON responses from the API.

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 in n8n credentials.

Troubleshooting

  • Error: "You must enter either 'prompt' or 'instrumental id'."
    This occurs if both or neither are provided. Provide exactly one of these inputs to proceed.

  • Task status errors ("failed", "cancelled", or timeout):
    When querying task status, if the task fails or is cancelled, the node throws an error indicating the failure. If the task does not complete after multiple attempts, it also errors out. Check the task ID validity and ensure the generation process completes successfully on the Mureka side.

  • Authentication errors:
    Ensure the API key credential is correctly set up and has necessary permissions.

  • Network issues:
    Verify network connectivity to the Mureka API endpoint.

Links and References

Discussion