Auto-log tl;dv meetings to Notion and a Google Sheet tracker

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.

Additional information

What does this prompt do?

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 do I need to use this?

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 can I 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.

Frequently asked questions

When does this run?

As soon as tl;dv finishes processing a new recording. You don't have to do anything; the workflow picks it up automatically.

Will it overwrite anything in my Notion database?

No. Each meeting becomes a brand-new page in the database you choose. Existing pages are never modified.

What goes into the Google Sheet row?

By default: meeting date, title, organizer, attendee count, duration, topic list, the link to your new Notion page, and the original tl;dv recording link. You can change the columns to match your sheet.

Can I include the full transcript in the Notion page?

By default the page captures the AI summary and topic list rather than the raw transcript. You can extend the workflow to pull the transcript too if you want it embedded.

What happens if a meeting fails to log?

Each run is independent, so a single failure won't block future meetings. You'll see the failed run in your workflow history and can retry it.