> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stackone.com/llms.txt
> Use this file to discover all available pages before exploring further.

# MeetGeek Webhook Setup Guide

> Configure MeetGeek to deliver events to StackOne.

## Prerequisites

The connector should already be set up, with a Connector Profile and a Linked Account. See [Getting Started](/connectors/meetgeek#getting-started) on the MeetGeek connector page.

## Send MeetGeek events to StackOne

MeetGeek sends one notification per recording, once its analysis has finished. Each StackOne connection has its own webhook address, which you paste into the MeetGeek account you linked. MeetGeek supports only one webhook address per account, so this replaces any address already configured there.

**1. Copy the Native Webhook URL from StackOne**

You can find the **Native Webhook URL** in the StackOne Hub or on the Linking Account form during account connection or linking.

<ul>
  <li>Copy the value from the **Native Webhook URL** field.</li>
  <li>The address identifies the account on its own, so there is no routing identifier to complete afterwards.</li>
</ul>

**2. Open Integrations in MeetGeek**

Sign in to your [MeetGeek account](https://app.meetgeek.ai) using the same account you linked to StackOne.

<ul>
  <li>Click **Integrations** under **PRODUCTIVITY** in the left-hand navigation, or open the [MeetGeek integrations page](https://app.meetgeek.ai/integrations) directly.</li>
</ul>

![MeetGeek left-hand navigation with Integrations highlighted](https://mintcdn.com/stackone-60/vAXEI224_wx41F-w/connectors/meetgeek/images/events-open-integrations.png?fit=max\&auto=format\&n=vAXEI224_wx41F-w\&q=85\&s=13dcc1d1069057d8deee1821d617005c)

**3. Open the MeetGeek API app**

The **Apps & Workflows** page opens on the **Apps** tab.

<ul>
  <li>Locate the **MeetGeek API** card — "Access meeting data programmatically via the MeetGeek public API".</li>
  <li>If the card is not visible, use the search box in the top right-hand corner to filter for `MeetGeek API`.</li>
  <li>Click the card to open its settings panel.</li>
</ul>

![Apps and Workflows page with the MeetGeek API card highlighted on the Apps tab](https://mintcdn.com/stackone-60/vAXEI224_wx41F-w/connectors/meetgeek/images/events-meetgeek-api-app.png?fit=max\&auto=format\&n=vAXEI224_wx41F-w\&q=85\&s=cf912b82cb6017c859086ed7a7b3bf26)

**4. Paste the Native Webhook URL**

The settings panel opens on the right, below the **API Key** field.

<ul>
  <li>Paste the **Native Webhook URL** you copied from StackOne into the **Webhook URL** field.</li>
  <li>Click outside the field. The value is saved as soon as the field loses focus, so there is no Save button to press.</li>
  <li>To stop delivery at any time, clear the field. MeetGeek then sends no notifications at all.</li>
</ul>

![MeetGeek API settings panel with the Webhook URL field highlighted](https://mintcdn.com/stackone-60/vAXEI224_wx41F-w/connectors/meetgeek/images/events-webhook-url.png?fit=max\&auto=format\&n=vAXEI224_wx41F-w\&q=85\&s=e455b5b50df55cf649d4932138180932)

## Available webhook events

The following MeetGeek events can be enabled. Only events selected in StackOne are delivered. MeetGeek has no event picker of its own — it sends every notification to the address you configured, and StackOne forwards only the events you have enabled.

**1. Meeting analysis events**

Events reporting the outcome of MeetGeek's analysis of a recording.

<ul>
  <li>**Meeting Analysed** (`meeting.analyzed`) — Fired when MeetGeek finishes analysing a recording, whether it came from a meeting its notetaker attended or from an uploaded file. Carries the meeting ID, so the transcript, summary, highlights and insights can be retrieved immediately.</li>
  <li>**Meeting Analysis Failed** (`meeting.analysis_failed`) — Fired when MeetGeek cannot analyse a recording, for example because the file could not be downloaded or was not an audio or video file. MeetGeek does not identify which recording failed, so this event carries no meeting ID.</li>
</ul>

## Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.