Whereby icon

Whereby

Interact with Whereby video conferencing API

Actions8

Recording → Get All

AI-generated

Overview

This node integrates with the Whereby video conferencing API to manage recordings. Specifically, the "Recording" resource with the "Get All" operation allows users to retrieve a list of all recordings associated with their account or organization.

Common scenarios for this node include:

  • Fetching all available video conference recordings for archival or review.
  • Automating workflows that process or analyze recorded meetings.
  • Integrating recording data into other systems such as CRMs or content management platforms.

For example, a user might use this node to pull all recordings from Whereby and then trigger a transcription service or notify team members about new recordings.

Properties

Name Meaning
Return All Whether to return all recordings or limit the number of results returned.
Limit The maximum number of recordings to return if "Return All" is set to false (minimum 1).
  • Return All: If true, the node fetches all recordings without limitation.
  • Limit: When "Return All" is false, this limits the number of recordings retrieved in one execution.

Output

The output is an array of JSON objects, each representing a recording retrieved from the Whereby API. Each item contains detailed information about a recording, such as its ID, metadata, timestamps, and possibly URLs or access details depending on the API response.

No binary data output is produced by this operation.

Example output structure (simplified):

[
  {
    "id": "recording-id-123",
    "meetingId": "meeting-id-456",
    "createdAt": "2024-01-01T12:00:00Z",
    "duration": 3600,
    "status": "available",
    ...
  },
  ...
]

Dependencies

  • Requires an active connection to the Whereby API via an API key credential configured in n8n.
  • The node uses HTTP requests to the Whereby REST API endpoints.
  • No additional external dependencies beyond the API key and internet connectivity.

Troubleshooting

  • API Authentication Errors: Ensure the API key credential is correctly configured and has sufficient permissions.
  • Rate Limits or Pagination Issues: If many recordings exist, consider using "Return All" carefully to avoid hitting API rate limits.
  • Empty Results: Verify that recordings exist in the Whereby account and that the API key corresponds to the correct organization.
  • Network or Timeout Errors: Check network connectivity and API availability.

If errors occur, the node can be configured to continue on failure, returning error messages per item for easier debugging.

Links and References

Discussion