Turn Plaud transcripts into Asana tasks
When Plaud finishes a meeting recording, an agent pulls out every real commitment and files it as an assigned Asana task with the right owner and due date.
Plaud
AsanaOperationsPersonal ProductivityMeeting WorkflowsDocument ProcessingBuild an agent workflow that turns finished Plaud meeting transcripts into assigned Asana tasks for every real action item.
Trigger: a Plaud webhook on the audio_transcribe.completed event. Only proceed when the workflow status is SUCCESS. Ignore FAILURE and REVOKED events.
Steps the agent should take:
1. Call Plaud Get Workflow Result using the workflow id from the webhook payload to pull the full transcript and any speaker labels.
2. Read the transcript and identify discrete action items. An action item must be a concrete deliverable with a verb and an outcome. Skip filler commitments like 'we should circle back sometime,' 'let's keep thinking about this,' or generic agreement. For each action item, capture: the action itself, the owner mentioned (spoken name), any explicit due date language such as 'by Friday' or 'before the QBR,' and the surrounding sentence or two of context that explains why this task exists.
3. Resolve owners to Asana users. Call Asana Get Users in a Workspace once to build a name-to-gid lookup for the configured workspace. Match each spoken name to a workspace user by first name, full name, or obvious nickname. If there is no confident match, leave the assignee blank instead of guessing.
4. For each kept action item, call Asana Create a Task in a pre-configured project (project gid is a config input). Set: name to a short imperative version of the action; notes to the surrounding context plus a quoted snippet from the transcript on its own line, prefixed with a quote marker; assignee to the matched Asana user gid when available; due_on to the resolved calendar date when a due date was clearly stated, otherwise leave it unset.
5. If no action items qualify, exit cleanly without creating anything.
Configuration inputs the workflow should expose: the Asana workspace gid, the destination Asana project gid, and an optional list of name aliases (for cases like 'Alex' meaning Alexandra Smith).
Quality bar: never invent a due date that was not stated. Never invent an assignee. One Asana task per real commitment, no duplicates inside the same transcript. The goal is that nothing actionable from a meeting is lost just because no one re-reads the transcript.
What does this prompt do?
- Listens for finished Plaud transcripts and reads the full conversation.
- Picks out only the real commitments, ignoring filler like 'we should circle back sometime.'
- Creates an Asana task for each action item with the owner, due date, and a quoted snippet from the meeting.
- Drops every task into a project you choose so follow-ups land in one place.
What do I need to use this?
- A Plaud account with the developer platform enabled and a meeting transcription workflow already in use.
- An Asana login with access to the project you want new tasks to land in.
- A short list of teammates the agent should match spoken names against.
How can I customize it?
- Point it at a different Asana project, or split tasks across projects by meeting type.
- Tighten or loosen what counts as a real action item, for example require an explicit owner or a clearly stated date.
- Change the task description format, like adding the meeting title, a link back to the recording, or a custom tag.
FAQs
Will every transcript create tasks, even casual chats?
How does it know who to assign each task to?
What if no due date was stated out loud?
Can I send tasks to more than one Asana project?
Does it overwrite or duplicate tasks if the same meeting is processed twice?
Related templates
One ledger per client account showing every promise your team made on a call, who owes it, and what is already overdue.
Rank your published archive by how badly each post is fading, see who is now out-covering you on the topic, and log a verdict for every one.
Open one board before standup that lists every task stuck behind unfinished work, ranked by how long it has been waiting, and chase the owner in a click.
Open one board every Monday to see every person's open Asana work across all projects, spot who is buried, and hand tasks over in a click.
One screen that ranks your projects by how long they have gone without an update, drafts each one for you, and rolls the set into a client-ready doc.
Every Monday, check each client's accounts and confirmation statement dates on the UK register, open tasks for what is due soon, and post the practice one clear status update.
Stop losing action items to transcripts no one re-reads.
Connect Plaud and Asana once, and Geni turns every finished meeting recording into assigned, dated tasks.