WherebyInstall

Overview

This node interacts with the Whereby video conferencing API, specifically managing recordings in this context. The "Delete Recording" operation allows users to delete a specific recording by its ID. This is useful for automating cleanup of old or unwanted recordings, managing storage, or enforcing retention policies.

Practical examples:

• Automatically deleting recordings after a certain period.
• Removing recordings that are no longer needed to free up cloud storage.
• Integrating with workflows that manage meeting lifecycle and associated recordings.

Properties

Output

The output JSON object confirms the success of the deletion operation and echoes back the recordingId that was deleted. It has the following structure:

{
  "success": true,
  "recordingId": "string"
}

• success: A boolean indicating whether the deletion was successful.
• recordingId: The ID of the recording that was deleted.

No binary data is output by this operation.

Dependencies

• Requires an active connection to the Whereby API using a valid API authentication token configured in the node credentials.
• The node uses HTTP DELETE requests to the /v1/recordings/{recordingId} endpoint of the Whereby API.

Troubleshooting

• Common issues:

  • Providing an invalid or non-existent Recording ID will likely result in an error from the API.
  • Network connectivity problems can cause request failures.
  • Insufficient permissions or expired API tokens may lead to authorization errors.

• Error messages and resolutions:

  • "Recording not found": Verify the Recording ID is correct and the recording exists.
  • "Unauthorized" or "Forbidden": Check that the API key credential is valid and has necessary permissions.
  • Network errors/timeouts: Ensure stable internet connection and that the Whereby API service is reachable.

Links and References

• Whereby API Documentation
• Whereby Recordings API Reference