WherebyInstall

Overview

This node integrates with the Whereby video conferencing API to manage meetings and recordings. Specifically, for the Meeting - Get operation, it retrieves detailed information about a specific meeting by its unique Meeting ID.

Common scenarios where this node is beneficial include:

• Fetching meeting details to display or log in other systems.
• Verifying meeting existence or status before performing further actions.
• Integrating Whereby meeting data into workflows such as notifications, reporting, or analytics.

Practical example:

• You have an automated workflow that triggers when a meeting ends, and you want to fetch the meeting's metadata (like start/end time, participants, URLs) to store in your CRM or send a summary email.

Properties

Output

The output is a JSON object containing the full details of the requested meeting as returned by the Whereby API. This typically includes properties such as meeting URLs, start and end times, room settings, recording and transcription configurations, and other metadata related to the meeting.

No binary data is output by this operation.

Example output structure (simplified):

{
  "id": "string",
  "hostRoomUrl": "string",
  "viewerRoomUrl": "string",
  "startDate": "ISO8601 timestamp",
  "endDate": "ISO8601 timestamp",
  "isLocked": false,
  "roomMode": "normal",
  "recording": {
    "type": "none"
  },
  "liveTranscription": {
    "startTrigger": null,
    "language": "en",
    "liveCaptions": false
  },
  ...
}

Dependencies

• Requires an API key credential for authenticating with the Whereby API.
• The node uses HTTP requests to the Whereby REST API endpoints.
• No additional external dependencies beyond the API access are needed.
• Ensure the API key has permissions to read meeting details.

Troubleshooting

• Error: Meeting not found or invalid Meeting ID
  This occurs if the provided Meeting ID does not exist or is mistyped. Verify the Meeting ID is correct and corresponds to an existing meeting.

• Authentication errors
  If the API key is missing, invalid, or lacks proper permissions, the request will fail. Check that the API key credential is correctly configured and active.

• Network or API downtime
  Temporary network issues or Whereby service outages can cause failures. Retry after some time or check Whereby's status page.

• Rate limiting
  Excessive requests may be throttled by the API. Implement retry logic or reduce request frequency.

Links and References

• Whereby API Documentation
• Whereby Meetings API Reference