Whereby icon

Whereby

Interact with Whereby video conferencing API

Actions8

Meeting → Delete

AI-generated

Overview

This node integrates with the Whereby video conferencing API to manage meetings and recordings. Specifically, for the Meeting - Delete operation, it allows users to delete an existing meeting by specifying its unique Meeting ID.

Common scenarios where this node is beneficial include:

  • Automating cleanup of obsolete or canceled meetings.
  • Integrating meeting lifecycle management into broader workflows, such as removing meetings after events conclude.
  • Managing meetings programmatically without manual intervention in the Whereby dashboard.

Example use case:

  • After a webinar finishes, automatically delete the associated meeting to free up resources and maintain organization.

Properties

Name Meaning
Meeting ID The unique identifier of the meeting to delete. This is required to specify which meeting should be removed.

Output

The output JSON object contains:

  • success: A boolean indicating whether the deletion was successful (true).
  • meetingId: The ID of the meeting that was deleted.

Example output:

{
  "success": true,
  "meetingId": "abc123"
}

This confirms the meeting identified by the given ID has been deleted.

Dependencies

  • Requires an active API authentication token credential for the Whereby API.
  • The node makes HTTP DELETE requests to the /v1/meetings/{meetingId} endpoint of the Whereby API.
  • No additional external dependencies are needed beyond the configured API credentials.

Troubleshooting

Common Issues

  • Invalid Meeting ID: If the provided Meeting ID does not exist or is malformed, the API will return an error.
  • Authentication Failure: Missing or invalid API credentials will cause authorization errors.
  • Network Issues: Connectivity problems can prevent the request from reaching the API.

Error Messages and Resolutions

  • "404 Not Found": The specified Meeting ID does not exist. Verify the ID is correct.
  • "401 Unauthorized": Authentication failed. Check that the API key or token is valid and properly configured.
  • "400 Bad Request": The request parameters are invalid. Ensure the Meeting ID is correctly formatted.
  • Timeouts or Network Errors: Retry the operation or check network connectivity.

Enabling "Continue On Fail" in the node settings can allow workflows to proceed even if deletion fails for some items.

Links and References

Discussion