Turn Google Meet action items into Asana tasks with a Slack recap

Every weekday at 6pm in my local time zone, sweep all of my Google Meet conference records from the last 24 hours, turn every real action item into an Asana task assigned to the right person with a due date, and post one tidy recap to a team Slack channel so we can scan the day's commitments in one place.

For the trigger, use a cron schedule (Google Meet does not have a real-time trigger here).

For each run, use Google Meet List Conference Records to pull every conference that ended in the last 24 hours. For each conference record, fetch the participant roster with List Participants, then List Transcripts to find any transcript document for the call, then List Transcript Entries to assemble the full transcript with speaker labels (name plus the line they said, in order). Skip any conference that has no transcript, and skip 1-on-1s that produce no action items so the recap stays useful.

Once you have the speaker-labeled transcript and the participant list for a meeting, reason about which lines are genuinely action items. Include concrete commitments and asks; skip 'we should think about that' musings, brainstorms, and rhetorical questions. For each action item, figure out the owner from speaker context and explicit cues like 'I'll', 'I will', 'I can take that', or 'Can you...' / 'Could you...' addressed to a specific participant. Infer a reasonable due date from phrases like 'by Friday', 'end of week', 'next sprint', or 'before our Tuesday standup', resolving them against the meeting's date. If the owner or due date is genuinely ambiguous, leave them blank rather than guessing.

For each action item, use Asana Create a Task in a designated project I will configure. The task name should be a clean one-line summary of the commitment. The task description should include the meeting title and date, the verbatim line that prompted the action item (quoted), and a link back to the Google Meet recording or transcript. Assign the task to the matching Asana user (resolve by name or email against the participant list) and set the due date if one was inferred. If the owner cannot be confidently matched to an Asana user, create the task unassigned and surface that in the Slack recap so a human can claim it.

Finally, use Slack Send a Message to post one recap to a team channel I will configure. The recap should list each processed meeting with its title, attendees, and a bulleted list of action items, each one showing the owner, the inferred due date if any, and a link to the Asana task that was created. Group everything under one message so the team can scan the day's commitments in one place. If no meetings had action items, post a short note saying the day was clear instead of staying silent.

Dedupe across runs: keep track of which conference records have already been turned into tasks (for example by storing the conference record ID after a successful run) so a re-run does not create duplicate Asana tasks or duplicate Slack recaps for the same meeting. Make the designated Asana project, the designated Slack channel, and the time zone easy for me to change later.