Overview
This node acts as a trigger for MeetGeek events, starting an n8n workflow when specific events occur in the MeetGeek platform. It listens for webhook notifications about new highlights or new meetings created in MeetGeek and triggers the workflow accordingly.
Common scenarios where this node is beneficial include:
- Automatically processing or analyzing meeting highlights as soon as they are created.
- Initiating follow-up actions or notifications when a new meeting is scheduled or recorded.
- Integrating MeetGeek event data into other systems or workflows without manual intervention.
For example, you could use this node to start a workflow that sends a summary email whenever a new highlight is created or to log meeting details into a CRM system when a new meeting occurs.
Properties
| Name | Meaning |
|---|---|
| Event Type | The type of MeetGeek event to listen for. Options: "New Highlight" (trigger on highlight creation), "New Meeting" (trigger on meeting creation). |
| Flow Name | A user-defined name for this webhook flow, used to identify the webhook subscription. |
Output
The node outputs the JSON payload received from the MeetGeek webhook in the json field of the output data. This payload contains the event data related to the selected event type (highlight or meeting).
No binary data is output by this node.
Dependencies
- Requires an API authentication token credential for MeetGeek (an API key).
- The node registers a webhook URL with MeetGeek's API to receive event notifications.
- The node dynamically selects the API base URL depending on the token prefix (e.g., US region or default).
- Proper configuration of the webhook URL in MeetGeek via the subscription API is necessary.
Troubleshooting
- Webhook registration failure: If the node cannot register the webhook with MeetGeek, it throws an error. Ensure the API token is valid and has the required permissions.
- Webhook not triggering: Verify that the webhook URL is accessible from MeetGeek and that the correct event type is selected.
- Deletion issues: If unsubscribing fails, the node will silently ignore errors but may leave orphaned webhooks in MeetGeek.
- Invalid token format: The node expects tokens starting with certain prefixes to determine the API endpoint; using an unsupported token format may cause failures.
Links and References
- MeetGeek official website
- MeetGeek API documentation (if publicly available)