Log every tl;dv meeting to Notion and Google Sheets
Every time tl;dv finishes a recording, file a Notion page in your meetings database and append a row to your master meeting log.
Integrations
tl;dv
Notion
Google Sheets
Type
Categories
- Operations
Build a deterministic code workflow that mirrors every new tl;dv recording into our team knowledge base in Notion and into a master meeting log in Google Sheets. The pipeline is fixed: every meeting gets exactly one Notion page and exactly one spreadsheet row. No judgement steps, no LLM branching.
Trigger: poll trigger on tl;dv with event type new_recording. The trigger fires when tl;dv finalizes a meeting recording and gives us the meeting ID.
Step 1: Call tl;dv Get Meeting with the meeting ID from the trigger to fetch metadata (title, happenedAt date, organizer, invitees/attendees, duration, recording URL, template).
Step 2: Call tl;dv Get Meeting Notes with the same meeting ID to fetch the AI-generated structured notes (markdown summary and the list of topics).
Step 3 (in parallel with Step 4): Call Notion Create a Page inside a configured Meetings database. Set the title to the meeting title. Map standard properties: Date (meeting date), Attendees (attendee names or emails), Organizer, Duration, Topics (multi-select or text from the topic list), and Recording Link (the tl;dv recording URL). Put the markdown summary and the topic breakdown into the page body so the page is fully readable on its own.
Step 4 (in parallel with Step 3): Call Google Sheets Append Values on a configured tracker sheet. Append exactly one row with these columns in order: meeting date, meeting title, organizer, attendee count, duration, topic list (joined), Notion page URL (from the Step 3 response), tl;dv recording link.
Configuration the user should be prompted for: tl;dv credential, Notion credential, Notion meetings database ID, Notion property mapping for Date / Attendees / Organizer / Duration / Topics / Recording Link, Google Sheets credential, spreadsheet ID, and worksheet/tab name.
Behavior: each meeting is processed independently. If the Notion step fails the sheet row should still be attempted, and vice versa, so a transient failure in one tool doesn't block the other. No deduplication beyond what the poll trigger already provides.
What it does
- Watches tl;dv for new finalized recordings and runs the moment one is ready.
- Pulls the meeting title, date, organizer, attendees, duration, and recording link, plus the AI-generated summary and topic list.
- Creates a new page in your Notion meetings database with all of that context, formatted and ready to read.
- Appends one row to your master Google Sheets meeting log so you have a complete, searchable history of every call.
What you’ll need
- A tl;dv account with API access enabled.
- A Notion workspace with a meetings database (and any properties you want filled in, like Date, Attendees, or Topics).
- A Google account with edit access to the spreadsheet you want to use as your meeting log.
How to customize it
- Point it at any Notion database and map your existing properties (date, attendees, topics, recording link).
- Pick which spreadsheet and tab to append to, and which columns each row should fill.
- Filter the trigger to only log meetings from a specific organizer, template, or workspace if you don't want every recording captured.
Use cases
- Data Sync
- Meeting Workflows
