MurekaInstall

Overview

This node interacts with the Mureka API to query the status and details of an instrumental music generation task. It is useful when you have previously started generating an instrumental track via Mureka's AI service and want to check the progress or retrieve the final result once ready.

Typical scenarios include:

• Monitoring the completion status of a long-running instrumental generation task.
• Retrieving metadata or output URLs related to a specific instrumental generation job.
• Automating workflows that depend on the availability of generated instrumental music.

For example, after triggering an instrumental generation, you can use this node operation to poll the task status until it completes successfully, then proceed to download or process the generated audio.

Properties

Output

The node outputs a JSON object representing the current state and details of the queried instrumental generation task. The structure typically includes:

• status: The current status of the task (e.g., "preparing", "queued", "running", "succeeded", "failed", "cancelled").
• Additional fields returned by the Mureka API about the task, such as progress information, result URLs, or error messages if applicable.

If the task is still in progress ("preparing", "queued", or "running"), the node will retry querying multiple times with delays until the task completes or a maximum number of attempts is reached.

No binary data output is produced by this operation.

Dependencies

• Requires an active API key credential for authenticating requests to the Mureka API.
• Network access to https://api.mureka.ai endpoints.
• The node uses built-in HTTP request helpers with authentication configured in n8n.

Troubleshooting

• Error: Task failed or cancelled
  If the task status returns "failed" or "cancelled", the node throws an error indicating the task did not complete successfully. Check the input parameters and the Mureka service dashboard for more details.

• Error: Task did not complete after maximum attempts
  The node polls the task status up to 20 times with 30 seconds delay between attempts. If the task remains incomplete after these retries, an error is thrown. Consider increasing wait time or verifying the task ID correctness.

• Invalid Task ID
  Providing an incorrect or non-existent Task ID will likely cause the API to return errors or no meaningful data. Ensure the Task ID matches one returned from a previous generation request.

• Network or Authentication Issues
  Failures in connecting to the API or invalid credentials will cause request errors. Verify your API key credential setup in n8n.

Links and References

• Mureka API Documentation (for detailed API endpoints and responses)
• n8n HTTP Request Node Documentation (for understanding requestWithAuthentication helper)