Actions8
- Meeting Actions
- Recording Actions
- Highlight Actions
- Team Actions
- Transcript Actions
Overview
This node integrates with the MeetGeek API to manage and retrieve information related to teams, meetings, recordings, highlights, and transcripts. Specifically, for the Team - Get Many operation, it fetches a list of teams associated with the authenticated user or organization. This is useful when you want to automate workflows that involve managing multiple teams, such as syncing team data with other systems, generating reports on team activities, or triggering actions based on team membership.
Practical example:
You could use this node to retrieve all teams in your MeetGeek account and then loop through each team to gather meeting statistics or send notifications to team members.
Properties
| Name | Meaning |
|---|---|
| Limit | Max number of results to return. Specifies how many teams to fetch from the API (minimum 1). |
Output
The output JSON contains an array of team objects under the root level. Each object represents a team with its properties as returned by the MeetGeek API. The exact structure depends on the API response but typically includes identifiers, names, and metadata about each team.
No binary data output is produced by this operation.
Dependencies
- Requires an API authentication token credential for the MeetGeek API.
- The node dynamically selects the API base URL depending on the token prefix (US or EU region).
- Uses HTTP GET requests to the
/v1/teamsendpoint of the MeetGeek API.
Troubleshooting
Common issues:
- Invalid or missing API token will cause authentication failures.
- Exceeding rate limits imposed by the MeetGeek API may result in errors or throttling.
- Providing a
limitvalue less than 1 will likely cause validation errors.
Error messages:
- Authentication errors usually indicate invalid credentials; verify the API token.
- Network or timeout errors suggest connectivity issues; check internet access and API availability.
- If no teams are returned, ensure the authenticated user has access to teams in their MeetGeek account.
Links and References
- MeetGeek API Documentation (for detailed API endpoints and data structures)
- n8n documentation on HTTP Request Node (conceptual similarity)