Actions8
- Meeting Actions
- Recording Actions
- Highlight Actions
- Team Actions
- Transcript Actions
Overview
This node interacts with the MeetGeek API to retrieve multiple transcript sentences associated with a specific meeting. It is designed to fetch either all available transcript data or a limited subset based on user preference. This functionality is useful for scenarios such as analyzing meeting content, generating summaries, or integrating meeting transcripts into other workflows.
For example, a user might want to automatically pull all transcript sentences from a recorded meeting to perform sentiment analysis or keyword extraction in subsequent steps of an automation.
Properties
| Name | Meaning |
|---|---|
| Meeting ID | The unique identifier of the meeting for which to retrieve transcript sentences. |
| Return All | Whether to return all transcript sentences available or only up to a specified limit. |
| Limit | The maximum number of transcript sentences to return if not returning all (minimum 1). |
Output
The node outputs a JSON array under the json field containing transcript sentences. Each item in the array represents a sentence from the meeting transcript. The structure corresponds to the API response's sentences array.
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 endpoint).
- Uses the n8n helper method for authenticated HTTP requests.
Troubleshooting
Common issues:
- Invalid or missing Meeting ID will cause the API request to fail.
- Exceeding rate limits or invalid API tokens will result in authentication errors.
- Pagination handling may cause incomplete results if "Return All" is false and the limit is set too low.
Error messages:
- Authentication failures typically indicate problems with the provided API token; verify the token validity and permissions.
- "Meeting not found" or similar errors suggest the Meeting ID does not exist or is inaccessible.
- Network or timeout errors may require checking connectivity or retrying later.
Links and References
- MeetGeek API Documentation (general reference for endpoints and authentication)
- n8n documentation on HTTP Request Node for understanding requestWithAuthentication usage