bookoly icon

bookoly

Interact with the bookoly API

Overview

The node integrates with the Bookoly API to combine multiple audio files into a single sound. It is useful when you want to merge several public audio URLs into one cohesive audio output, for example, combining different sound clips or effects into a single track.

Typical use cases include:

  • Creating a custom sound effect by merging various audio snippets.
  • Combining multiple voice recordings or music tracks into one file.
  • Automating audio processing workflows where multiple audio sources need to be unified.

Properties

Name Meaning
Name The name assigned to the combined sound output.
Audio A collection of public and downloadable audio URLs to be combined. Multiple URLs can be added and sorted.
Wait for Completion If enabled, the node waits until the sound combination process finishes on the server and returns full details. If disabled, it returns only the ID and creation timestamp immediately.
Webhook URL An optional URL to receive webhook notifications about the sound generation status, including sound ID and URL.

Output

The node outputs JSON data representing the combined sound object returned from the Bookoly API. When "Wait for Completion" is enabled, this includes detailed information about the completed sound such as its ID, URL, and metadata. If waiting is disabled, the output contains minimal information like the sound ID and creation timestamp.

If the node supports binary data (not explicitly shown in the code), it would typically represent the combined audio file itself, but here the focus is on JSON metadata referencing the combined sound.

Dependencies

  • Requires an active connection to the Bookoly API via an API key credential.
  • The node expects publicly accessible and downloadable URLs for input audio files.
  • Optional webhook URL support requires a valid external endpoint to receive callbacks.
  • No additional environment variables are indicated beyond standard API authentication.

Troubleshooting

  • No handler found error: This occurs if the specified resource-operation pair does not have an implemented handler. Ensure that "Sound" resource and "Combine Sounds" operation are selected correctly.
  • Invalid or inaccessible audio URLs: The node requires publicly downloadable URLs. Private or restricted URLs will cause failures.
  • Timeouts or incomplete results: If "Wait for Completion" is enabled but the server takes too long, consider disabling it or verifying the webhook URL setup.
  • Webhook delivery issues: If webhook notifications are not received, check the validity and accessibility of the provided webhook URL.

Links and References

Discussion