---
title: "Send meetings to Obsidian or a folder"
description: "Have Recordstead write each meeting into an Obsidian vault or a folder by itself, and keep it up to date."
updated: "2026-10-18"
canonical: https://docs.recordstead.app/meetings/send-to-obsidian-or-a-folder
---

# Send meetings to Obsidian or a folder

Recordstead can write each meeting into your Obsidian vault, or into any folder, by itself once processing is done. Obsidian does not need to be open. To run a shortcut or a script instead, see [Run a shortcut or a command for each meeting](https://docs.recordstead.app/automation/run-a-shortcut-or-command).

## Set up an integration

1. Open **Settings** (⌘,) › **Integrations**.
2. Click **+** under the list and choose **Obsidian Vault** or **Folder**.
3. Click **Choose…** and pick the folder. For Obsidian, pick a folder inside your vault; the sheet names the vault it found.
4. Under **What to send**, turn off what you don't want written.
5. Click **Save**.

**Your result:** each meeting you record or add from now on appears there, as a note in Obsidian or as Markdown files in a folder. The row shows when it last sent. A meeting that was already recording or processing when you set it up goes with **Send Earlier Meetings**, below.

## Choose when, and which meetings

- **Send when**: **Processing is done** waits for the summary and your tasks. **Recording stops** writes the note at once; a file you add yourself is never sent at that moment.
- **Workspaces** sends only the meetings of the workspaces you choose.
- **Keep notes up to date** writes a meeting again about 30 seconds after it changes: a new title, renamed speakers, a new summary, your notes. A note you changed in Obsidian is left as it is, and a note you deleted is not written again.

A note keeps its first file name. If you move it inside the vault, Recordstead still finds it.

## Send the meetings you already have

Select the integration, click **⋯** and choose **Send Earlier Meetings**. Meetings that finished while an integration was turned off are sent this way too.

## Change how the note looks

Click **Edit…** next to **Note layout**. Each `{{variable}}` is filled in for every meeting, in the syntax of Obsidian's Templates, so `{{date:DD.MM.YYYY}}` works. A summary is always followed by a hidden record of how it was made, as in an export.

## If a meeting is not sent

The row says why, for example that the folder can't be found, and when it tries again. Fix the folder, then choose **Try Again** in **⋯**.

With **Processing is done**, a meeting whose summary failed waits, and the row does not show it. Use **Generate** on the meeting’s Summary step; once the summary is made, the meeting is sent.