Skip to content
← Help

Integrations: send your meetings anywhere

When a meeting is done, Daisy can push it out of the app — to a chat channel, an automation tool, your own server, or a Markdown folder. You set up destinations once, then send to them by hand (one meeting, on demand) or automatically (with a Workflow).

What do you want to do?

You want to… How Daisy does it
Post to Slack / Discord / Teams A webhook destination pointed at that channel's incoming-webhook URL
Automate with n8n / Zapier / Make A webhook destination pointed at your flow's webhook URL — the other side decides what happens next
Hit your own server / endpoint A webhook destination (https://, or http://localhost for a local tool)
Save to an Obsidian / Markdown vault Not a webhook — use Export .md on a meeting (manual), or a Workflow that writes the analysis to your vault folder (automatic). See below

Integrations are webhooks — a single JSON POST. Slack, Zapier, n8n and the rest are just the receiver on the other end; there's no separate connector to install, and nothing of yours is stored by us in between.

Add a destination

  1. Open Settings → Integrations, select + Add destination.
  2. Fill in:
    • Name — a label you'll recognize ("Slack — team notes").
    • Webhook URL — an https:// address, or http://localhost for a local tool like n8n.
    • Auth — none, a custom header (e.g. X-API-Key), or a bearer token.
    • Include in the payload — tick any of summary, notes, transcript (at least one).
    • enabled — leave on so it appears in Send To… on a meeting.
  3. Save. Add as many as you like.

Auth secrets are write-only — once saved, the header value or token is never shown again. When editing, choose keep current to leave it in place.

Send a meeting (by hand)

  1. Open the meeting.
  2. Open the Action menu (▾) and choose ↗ Send To….
  3. Pick a destination. A green ✓ appears once it's been sent.

Only enabled destinations show up. If the menu says "Define in Settings → Integrations," you don't have one yet.

What gets sent

A single JSON POST containing a meeting block (id, title, start time, duration, tags, attendees) plus whichever of summary / notes / transcript you enabled — each as Markdown. That's the whole payload; it isn't templatable.

Save to a Markdown vault

There's no "vault" destination type — writing Markdown to a folder happens two ways:

  • Export .md (Action menu) — a Save-As dialog that writes the meeting's summary to a .md file wherever you choose. One meeting at a time.
  • A Workflow, for a vault that fills itself: a Run prompt → also write to folder step auto-writes the prompt's analysis output as a .md file into a folder you pick (point it at your Obsidian vault). See Workflows.

Do it automatically

To send or save without clicking each time, wrap it in a Workflow — e.g. when a recording tagged Client A is finalized, send it to your webhook. Every manual send is logged too — see Reviewing what was sent.