File Linear issues from meeting action items with OpenClaw
Extract action items from meeting notes and file them as Linear issues with OpenClaw: team-scoped creation requires team UUID lookup.
· 3 min read
Turn meeting action items into tracked Linear issues with OpenClaw. Extract tasks from meeting notes, confirm with the user, then create issues in the right team with proper assignees and states.
First-time Linear setup with OpenClaw requires connecting Linear through ClawLink. This guide covers creating issues from action items after the connection works.
How to turn action items into Linear issues
- Ask OpenClaw to extract action items from your meeting notes or transcript
- Ask OpenClaw to list the issues and wait for your yes before creating anything
- Confirm creation and OpenClaw files each item as a Linear issue
- Issues appear in Linear with titles, descriptions, and team assignments
Start with meeting notes from any source: Notion, Google Docs, or plain text. Ask OpenClaw to extract action items from a meeting transcript.
Extract and create issues
Tell OpenClaw to find action items and prepare Linear issues:
Extract action items from these meeting notes and prepare Linear issues for the Engineering team. List what you found and ask me to confirm before creating anything.
OpenClaw reads the notes, identifies actionable tasks, and shows you the proposed issues. It lists teams by name first to match "Engineering team" to the actual team UUID, then shows each issue it plans to create with title, description, and team assignment.
Review the list. Action items become issue titles, meeting context becomes descriptions, and team names get resolved to Linear team IDs.
Confirm before creating
Ask OpenClaw to list the issues and wait for your yes before creating anything. This prevents accidental creation and lets you review titles, descriptions, and assignments.
The confirmation step is user-controlled, not enforced by ClawLink. OpenClaw sends confirmed=true by default when calling create tools, so the human gate happens in the conversation, not in the API call.
After you confirm, OpenClaw calls linear_create_linear_issue for each action item using the team UUID it looked up earlier.
What team and assignment details need UUIDs?
Linear issue creation requires team UUID, not the team name people use in conversation. OpenClaw can look up the team UUID with linear_list_linear_teams to match "Engineering" or "Design" to the actual team UUID.
Assignees, states, and cycles also need UUIDs. All of these must belong to the same team as the issue being created. A person or state from another team fails. Name them in conversation so OpenClaw can look them up:
File these as issues for the Mobile team, assign to Sarah Chen, and set priority to high.
OpenClaw resolves "Mobile team" through linear_list_linear_teams and finds Sarah Chen's UUID with linear_list_linear_users.
Meeting context as issue descriptions
Action items extracted from meeting notes include context from the discussion if you ask, and only from what the notes say. OpenClaw creates issue descriptions that reference the original meeting, decision points, and any constraints mentioned in the notes.
For connected meeting notes workflows, link to the notes organization guide to capture meeting content before extracting action items.
FAQ
Can OpenClaw create issues without confirmation?
OpenClaw can create issues directly by calling linear_create_linear_issue, but the human confirmation step prevents accidental filing. Ask OpenClaw to "show me the issues first" or "confirm before creating" to maintain control over what gets filed.
Why does issue creation need team UUID instead of team name?
Linear's API needs the team UUID to create an issue. Team keys like ENG work for referencing existing issues (ENG-123), but new issue creation needs the full UUID. OpenClaw can look up the team UUID with linear_list_linear_teams.
Can action items go to different teams?
Yes. Extract action items that span multiple teams and OpenClaw creates issues in the appropriate team for each task. It resolves each team name separately and creates issues with the correct team UUID for each one.
What happens if an assignee name matches multiple people?
OpenClaw uses linear_list_linear_users to find assignees by name. If multiple people have similar names, specify the full name or ask OpenClaw to list team members first so you can confirm the right person before creating issues.
Do meeting action items preserve priority and due dates?
Action items become Linear issues with default priority and no due date unless you specify them. If the meeting notes mention deadlines or priority levels, include those in your instruction: "file as high priority with due date next Friday."
Can I batch create issues from multiple meetings?
Yes. Combine action items from several meetings and OpenClaw creates them one at a time. Issue descriptions include meeting details if you ask, and only from what the notes say.