Skip to content
← Help

Workflows: automate what happens to a recording

A Workflow turns something you'd do by hand into something Daisy does on its own. Each one is a rule: When something happens to a recording, If it matches your conditions, Do one or more actions. Rules run locally in the background — building one sends nothing off your machine.

Open Workflows from the navigation and select New workflow. It has four parts.

When — the trigger

One event starts a workflow:

  • Recording finalized — a recording finished processing and its transcript is ready. This is the only trigger where the transcript exists, so it's the one that can run prompts.
  • Recording deleted
  • Session imported
  • Processing failed

If — the conditions

Optional filters, combined as ALL of / ANY of (you can nest groups):

  • Tag is …
  • Participant is …
  • Title contains …

Leave conditions empty and the workflow runs for every recording.

Do — the actions

One or more steps, run in order:

  • Run prompt — run one of your Analyzer prompts over the transcript; the result is saved with the meeting. Optionally also send it to an integration, and/or also write to a folder as a .md file — point that at your Obsidian vault to fill it automatically. Run prompt is only available on the "Recording finalized" trigger, since the others have no transcript.
  • Send to integration — POST the meeting to a webhook destination. On Recording finalized it sends the content the destination is configured for; on the other triggers it sends event details only (title, tags, ids).

Save it. Workflows are listed under Active / Inactive with an Enabled toggle, and every run is logged so you can see what happened.

What stays private

Building or saving a workflow sends nothing. A workflow only reaches the network when an action does:

  • Send to integration → an outbound POST to your webhook URL.
  • Run prompt → runs through the AI provider you chose. A local model (LM Studio, Ollama) keeps it on your machine; your own cloud key sends the transcript text to that provider. Same choice as any analysis — see the FAQ.

Integration secrets stay in your encrypted vault, and workflows run only while the vault is unlocked.

Examples

  • When a recording tagged Client A is finalized → run your "design spec" prompt → send to your webhook.
  • When any recording is finalized → run "action items" → write to your Obsidian vault folder.
  • When processing fails → send to a webhook so your monitoring picks it up.