Recued
Menu
← Back to recipes

File meeting notes to vault

by recued-core v4 44 views

Use “File meeting notes to vault” in Recued. Files notes you captured during a meeting as a markdown note in the vault, headed with the matching calendar event's title and time, and records a provenance link from the event to the note. Paste the notes into the notes variable and name the event with eventid.

How it works 36 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (36 steps)
■ window date_period
Apply date_period
■ since date_parse
Parse window start as a date
■ until date_parse
Parse window end as a date
■ notes_present compare
Check if setting notes has data
■ vault_unset compare
Check if setting vault slug is empty
■ wants_event compare
Check if setting event id has data
◆ events core.data.calendar.list
List data calendar
skip: step.notes_present not_equal true
■ event_records default
Apply default
■ matched filter
Filter by condition
skip: step.wants_event not_equal true
■ matched_rows default
Apply default
■ match_count count
Count items in matched rows
■ event_found compare
Check if match count is greater than
■ matched_timed map
Extract from each item
■ matched_titles pluck
Extract summary from each item
■ event_title join
Join items with ", "
■ matched_times pluck
Extract starts_text from each item
■ event_time join
Join items with ", "
■ resolved_title coalesce
Use the first available value from: setting title, event title, Meeting
■ title_present compare
Check if resolved title has data
■ safe_title replace
Replace text in resolved title
■ note_date date_format
Format as a date
■ note_path template
Generate text from a template
◆ existing_stat core.storage.file.stat
Stat storage file
skip: step.vault_unset equal true
■ already_exists compare
Check if existing stat exists equals
■ note_body template
Generate text from a template
■ body_present compare
Check if setting notes has data
■ skip_write any
Check if any of the conditions are true
■ note_b64 encode_base64
Apply encode_base64
skip: step.skip_write equal true
◆ write core.storage.file.write
Write storage file
skip: step.skip_write equal true
■ written not
Apply not
■ skip_link any
Check if any of the conditions are true
◆ link core.memory.link.create
Create memory link
skip: step.skip_link equal true
■ linked not
Apply not
◆ final_stat core.storage.file.stat
Stat storage file
skip: step.vault_unset equal true
■ final_size default
Apply default
■ card to_summary
Format results as a summary card
▼
Output
summary card
copyable note_body
json matched_rows
Settings 7 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

notes setting =
title setting =
period setting = today
event id setting =
note dir setting = Meetings
vault slug setting =
calendar slug setting =

Uses (4 operations)

Calendar List data calendar core.data.calendar.list
Files Stat storage file core.storage.file.stat
Files Write storage file core.storage.file.write
Memory Create memory link core.memory.link.create

Trust & control

What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.

What it's allowed to do

Read Calendar core.data.calendar.list read-only
Read Files core.storage.file.stat read-only
Write Files core.storage.file.write external change
Write Memory core.memory.link.create external change

Data it touches

SurfacesCalendarFilesMemory
Warehousedata.calendardata.vault

About

Tags

pack:pkm-vaultpkmvaultmeetingnotesmarkdowncalendarprovenance

Details

36 steps 7 configurable settings recipe_id: file-meeting-notes-to-vault