Meeting → Get All
AI-generatedOverview
This node integrates with the Whereby video conferencing API to manage meetings and recordings. Specifically, the "Meeting - Get All" operation retrieves a list of all meetings associated with the authenticated account. It supports fetching either all meetings or a limited number based on user input.
Common scenarios for this node include:
- Synchronizing meeting data from Whereby into other systems.
- Displaying a list of upcoming or past meetings in dashboards or reports.
- Automating workflows that depend on the current set of meetings, such as sending reminders or generating summaries.
For example, you could use this node to fetch all meetings scheduled in your organization and then trigger follow-up emails to participants.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all meetings or only up to a specified limit. Options: true or false. |
| Limit | The maximum number of meetings to return when "Return All" is set to false. Must be at least 1. Default is 50. |
Output
The output consists of an array of JSON objects, each representing a meeting retrieved from the Whereby API. Each object contains detailed information about a meeting, such as its ID, start and end times, room URLs, and configuration settings.
The structure corresponds directly to the API response for meetings. When "Return All" is enabled, all meetings are returned; otherwise, only up to the specified limit are included.
No binary data output is produced by this operation.
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 environment variables are required beyond the API authentication setup.
Troubleshooting
Common issues:
- Authentication errors if the API key is missing or invalid.
- Rate limiting by the Whereby API if too many requests are made in a short time.
- Network connectivity problems preventing API calls.
Error messages:
- Errors returned from the API will be passed through, often including HTTP status codes and messages.
- If "Continue On Fail" is disabled, the node execution will stop on the first error.
- To handle intermittent failures gracefully, enable "Continue On Fail" to receive error details per item.
Resolutions:
- Verify that the API key credential is correctly configured and has necessary permissions.
- Check network connectivity and firewall settings.
- Respect API rate limits by adjusting workflow frequency or implementing retries.