Actions8
- Meeting Actions
- Recording Actions
- Highlight Actions
- Team Actions
- Transcript Actions
Overview
This node integrates with the MeetGeek API to retrieve detailed information about meetings and related entities such as recordings, highlights, teams, and transcripts. Specifically, the "Get Meeting Details" operation fetches comprehensive data for a single meeting identified by its unique Meeting ID.
Common scenarios where this node is useful include:
- Automatically retrieving meeting metadata after a meeting ends.
- Integrating meeting details into CRM or project management tools.
- Triggering workflows based on specific meeting attributes or statuses.
For example, after a sales call recorded in MeetGeek, you can use this node to get the meeting details and then update your sales pipeline accordingly.
Properties
| Name | Meaning |
|---|---|
| Meeting ID | The unique identifier of the meeting to retrieve. This is required to specify which meeting's details to fetch. |
Output
The output JSON contains the full details of the requested meeting as returned by the MeetGeek API. This typically includes metadata such as meeting title, participants, start and end times, recording links, summaries, and other relevant meeting information.
No binary data is output by this operation.
Dependencies
- Requires an API authentication token credential for the MeetGeek API.
- The node automatically selects the API base URL depending on the token prefix (US or EU region).
- No additional environment variables are needed beyond the configured API credential.
Troubleshooting
- Invalid Meeting ID: If the provided Meeting ID does not exist or is malformed, the API will return an error. Verify the Meeting ID is correct.
- Authentication Errors: Ensure the API token credential is valid and has necessary permissions.
- Network Issues: Connectivity problems may cause request failures; check network access to the MeetGeek API endpoints.
- Rate Limits: Excessive requests might be throttled by the API; consider adding delays or handling rate limit errors gracefully.
If the node throws errors, enabling "Continue On Fail" can help process multiple items without stopping the entire workflow.
Links and References
- MeetGeek API Documentation (for detailed API endpoint info)
- n8n HTTP Request Node Documentation (for understanding request options)