MeetGeek icon

MeetGeek

Interact with MeetGeek API
Join our community

Actions8

Overview

This node integrates with the MeetGeek API to retrieve multiple meeting records. It is designed to fetch a list of meetings either by returning all available meetings or limiting the number of results returned. This functionality is useful for scenarios such as aggregating meeting data for reporting, syncing meetings into other systems, or processing batches of meetings for further automation.

For example, you might use this node to:

  • Retrieve all meetings from your MeetGeek account to analyze attendance trends.
  • Fetch a limited number of recent meetings to display summaries in a dashboard.
  • Automate workflows that process meeting data in bulk.

Properties

Name Meaning
Return All Whether to return all meeting results or only up to a specified limit.
Limit The maximum number of meeting results to return when "Return All" is set to false. Minimum value is 1.

Output

The output JSON contains a field named meetings which is an array of meeting objects retrieved from the MeetGeek API. Each object represents a single meeting with its associated details as provided by the API.

The node does not output binary data.

Example structure of the output JSON:

{
  "meetings": [
    {
      "id": "string",
      "title": "string",
      "start_time": "string",
      "end_time": "string",
      "participants": [...],
      ...
    },
    ...
  ]
}

Dependencies

  • Requires an API key credential for authenticating with the MeetGeek API.
  • The node dynamically selects the API base URL based on the token prefix (US or EU region).
  • No additional external dependencies are required beyond the MeetGeek API access.

Troubleshooting

  • Common issues:

    • Invalid or missing API authentication token will cause request failures.
    • Exceeding API rate limits may result in errors or incomplete data retrieval.
    • Providing an invalid limit (e.g., less than 1) will likely cause validation errors.

  • Error messages and resolutions:

    • Authentication errors: Verify that the API key credential is correctly configured and has necessary permissions.
    • Pagination issues: If the node returns fewer results than expected, check if the "Return All" option is disabled and the limit is set too low.
    • Network or API endpoint errors: Ensure network connectivity and that the correct regional API endpoint is used automatically by the node.

Links and References

Discussion