MeetGeek icon

MeetGeek

Interact with MeetGeek API

Actions8

Overview

This node integrates with the MeetGeek API to retrieve information related to teams and their meetings. Specifically, the "Get Team Meetings" operation fetches all meetings associated with a specified team. This is useful for users who want to automate workflows involving team meeting data, such as aggregating meeting details for reporting, syncing meetings with other tools, or triggering actions based on team meeting events.

Practical example:
A user can input a Team ID to get a list of all meetings for that team, then use this data to generate summaries, send notifications, or analyze meeting frequency and participation.

Properties

Name Meaning
Team ID The unique identifier of the team whose meetings you want to retrieve. This must be provided to specify which team's meetings to fetch.

Output

The output is a JSON object containing the meetings associated with the specified team. The structure corresponds to the API response from the endpoint /v1/teams/{teamId}/meetings. It typically includes an array of meeting objects with details such as meeting IDs, titles, timestamps, participants, and other metadata relevant to each meeting.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the MeetGeek API.
  • The node dynamically selects the API base URL depending on the token prefix (US or EU region).
  • Network access to the MeetGeek API endpoints is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing Team ID will cause the API request to fail.
    • Authentication errors if the API key credential is incorrect or expired.
    • Network connectivity problems may prevent successful API calls.
  • Error messages and resolutions:

    • Authentication failed: Verify that the API key credential is correctly configured and valid.
    • Team not found or invalid Team ID: Confirm the Team ID is correct and that the authenticated user has access rights to that team.
    • Rate limiting or API errors: Check API usage limits and retry after some time or handle errors gracefully in the workflow.

Links and References

Discussion