Auto-create Asana tasks from Google Meet transcripts with a daily 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.

Additional information

What does this prompt do?

Reviews every Google Meet call from the last 24 hours and pulls the transcript with speaker labels so nothing said gets lost.
Picks out the real action items from the chatter, figures out who owns each one, and infers a reasonable due date from cues like 'by Friday' or 'next sprint.'
Files each action item as an Asana task in your team's project, assigned to the right person, with the verbatim quote and a link back to the recording.
Posts one clean Slack recap to your team channel listing every meeting, who attended, and the action items with their Asana links, so everyone can scan the day's commitments in one place.

What do I need to use this?

A Google Workspace account that hosts meetings with Google Meet recording and transcription turned on.
An Asana workspace and a target project where the action item tasks should land.
A Slack workspace and the channel where you want the daily recap posted.
Roughly which Asana person matches each Google Meet attendee, so owners get tagged correctly.

How can I customize it?

Change the run time, frequency, or look-back window (for example weekly on Friday afternoons instead of every weekday at 6pm).
Point tasks at a different Asana project, switch to subtasks under a parent, or add a default tag, section, or custom field.
Swap the Slack channel, send a DM to a team lead instead, or split the recap so each manager gets their team's items.
Tighten or loosen what counts as an action item, ignore certain meetings by title keyword, or skip recurring 1-on-1s entirely.

Frequently asked questions

Will this pick up action items from meetings I did not host?

It works on any Google Meet call your account has access to and that produced a recorded transcript. If you joined as a guest of an outside org, the transcript may not be visible to you, in which case those meetings are skipped.

What if my team does not record every meeting?

Only meetings with a transcript get processed. Untranscribed calls are silently skipped, so turning on recording for the meetings you care about is the easiest way to get more out of this workflow.

How does it decide who owns each task?

The agent reads the surrounding conversation and looks for cues like 'I'll handle that' or 'Can you take this?', then matches the speaker or addressee to a person in your Asana workspace. If the owner is genuinely unclear, the task gets created unassigned and flagged in the Slack recap.

Can I keep 1-on-1s and sensitive meetings out of it?

Yes. You can tell it to skip meetings by title pattern (for example anything containing '1:1' or 'private'), or only process meetings on specific calendars or in certain Google Meet spaces.

Will it create duplicate tasks if the same meeting gets processed twice?

No. It tracks which meetings it has already turned into tasks so a re-run will not duplicate yesterday's action items. You can also tell it to update existing tasks if the recording got re-processed with a corrected transcript.