Step-by-step: connecting MeetGeek to our Notion wiki

Hey folks! 👋 I've been using MeetGeek for a few months to automatically capture meeting notes, and it's been a game-changer for our stand-ups and retrospectives. But I kept hitting a wall: those great summaries and action items were just sitting in MeetGeek, while our team's single source of truth is our Notion wiki.

So I decided to wire them up! Here's the step-by-step I followed to get meeting summaries and transcripts flowing automatically into a dedicated Notion database.

### The Basic Setup
First, you'll need to create a Notion integration and a target database.

1. **Create a Notion Integration:**
* Go to [ https://www.notion.so/my-integrations ]( https://www.notion.so/my-integrations).
* Click "New integration," give it a name (e.g., "MeetGeek Connector"), and associate it with your workspace.
* **Copy the "Internal Integration Secret"** – you'll need this later.

2. **Create & Share a Notion Database:**
* Create a new page or database in Notion. I used a simple table with these properties:
* **Title** (default)
* **Date** (Date property)
* **Meeting Link** (URL property)
* **Summary** (Text property)
* **Transcript** (Text property – for the full text if needed)
* Share the database with your integration! Click 'Share' on the database page, invite your integration by its name, and give it 'Edit' access.

### The Automation Layer
MeetGeek has a built-in Zapier integration, which is the easiest path. Here's the Zap I built:

* **Trigger:** "New Meeting Summary" (MeetGeek)
* **Action:** "Create Database Item" (Notion)

The key is mapping the fields correctly in Zapier. My configuration looks like this in the action step:

```json
"Database": "Your Notion Database ID",
"Title": "{{MeetingTitle}} - {{Date}}",
"Date": "{{Date}}",
"Meeting Link": "{{MeetingUrl}}",
"Summary": "{{Summary}}"
```

You can also use the "Transcript" variable if you want the full text.

### Pro-Tip: Using Make (Integromat) for More Control
If you need more complex logic (like filtering for only certain types of meetings or formatting the summary with Markdown), I'd recommend using Make.com. You can use their HTTP module to call the Notion API directly. Here's a snippet of the kind of JSON you'd send:

```json
{
"parent": { "database_id": "YOUR_DB_ID" },
"properties": {
"Title": {
"title": [{ "text": { "content": "{{meeting.title}}" } }]
},
"Date": {
"date": { "start": "{{meeting.date}}" }
}
},
"children": [
{
"object": "block",
"type": "paragraph",
"paragraph": {
"rich_text": [{
"type": "text",
"text": { "content": "{{meeting.summary}}" }
}]
}
}
]
}
```

### Gotchas & Pitfalls
* **Rate Limits:** Be mindful of Notion's API rate limits if you have a *lot* of meetings.
* **Formatting:** Notion's API can be picky about date formats and rich text. Zapier handles this well, but if you're building a custom integration, test thoroughly.
* **Selective Sync:** Consider adding a filter in your Zap/Make scenario to only sync meetings from certain calendars or with specific keywords if you don't want *everything* in your wiki.

It's been running solidly for our team for a few weeks now, and having a searchable archive of meeting outcomes right where we do our planning is incredibly powerful.

Has anyone else set up a similar pipeline? I'm curious if you've added extra steps, like tagging action items or sending notifications to Slack based on the Notion entry.

~CloudOps