MurekaInstall

Overview

This node interacts with the Mureka API to query information about AI-generated music tasks specifically related to songs. It allows users to follow up on the status and results of previously submitted song generation tasks by providing a Task ID. This is useful in workflows where asynchronous music generation occurs, and you need to check if the task has completed, failed, or is still processing.

Practical examples include:

• Checking the completion status of a song generation request.
• Retrieving the generated song data once the task is finished.
• Handling task failures or cancellations gracefully in an automated workflow.

Properties

Output

The output is a JSON array containing the response from the Mureka API about the queried song task. The structure includes fields such as:

• status: The current status of the task (e.g., "preparing", "queued", "running", "succeeded", "failed", "cancelled").
• Additional metadata and result data returned by the API when the task is complete.

If the task is successful, the output will contain detailed information about the generated song. If the task is still running, the node waits and retries until completion or failure.

No binary data output is produced by this operation.

Dependencies

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

Troubleshooting

• Common issues:

  • Providing an invalid or expired Task ID will cause the API to return errors or no results.
  • Network connectivity problems can prevent querying the API.
  • If the task does not complete within the retry limit (20 attempts with 30 seconds delay each), the node throws an error.

• Error messages:

  • Task <ID> failed. — The song generation task failed on the server side.
  • Task <ID> cancelled. — The task was cancelled before completion.
  • Task <ID> did not complete after 20 attempts. — The task did not finish within the allowed polling attempts; consider increasing wait time or checking task validity.

To resolve these errors:

• Verify the Task ID correctness.
• Ensure stable internet connection.
• Check your Mureka API usage limits and credentials.
• Adjust workflow timing if necessary to allow longer task completion.

Links and References

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