Actions8
- Meeting Actions
- Recording Actions
- Highlight Actions
- Team Actions
- Transcript Actions
Overview
This node interacts with the MeetGeek API to retrieve multiple highlight entries associated with a specific meeting. It is designed to fetch either all highlights or a limited number of them for a given meeting ID. This functionality is useful in scenarios where users want to analyze, summarize, or process key moments from recorded meetings automatically.
Practical examples include:
- Extracting important discussion points from a meeting for reporting.
- Feeding highlights into other workflows such as notifications or documentation generation.
- Aggregating meeting insights across multiple sessions.
Properties
| Name | Meaning |
|---|---|
| Meeting ID | The unique identifier of the meeting for which highlights are to be retrieved. |
| Return All | Whether to return all available highlight results (true) or limit the number returned (false). |
| Limit | The maximum number of highlight results to return when Return All is set to false. |
Output
The node outputs an array of highlight objects under the json field. Each object represents a single highlight extracted from the specified meeting. The exact structure of each highlight object depends on the MeetGeek API response but typically includes details such as timestamp, content snippet, and relevance metadata.
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 based on the token prefix (US or EU region).
- Uses the n8n helper method for authenticated HTTP requests to the MeetGeek API.
Troubleshooting
Common issues:
- Invalid or expired API token will cause authentication failures.
- Providing an incorrect or non-existent Meeting ID will result in empty or error responses.
- Setting
Return Alltotruemay lead to longer execution times if many highlights exist.
Error messages:
- Authentication errors typically indicate invalid credentials; verify and update the API token.
- "Meeting not found" or similar errors suggest the Meeting ID does not exist or is inaccessible.
- Rate limiting or network errors can occur; retry after some time or check network connectivity.
Links and References
- MeetGeek API Documentation (for detailed API endpoints and data structures)
- n8n Documentation on Creating Custom Nodes