Imagine you are a **Technical Project Manager** or **DevOps Lead** juggling six hours of recorded meetings every day. You have the transcripts, but your project tracker requires structured data: who is doing what, by when, and what was decided. Manually reading through a **5,000-word transcript** to find three action items is like looking for a needle in a haystack while the haystack is growing. This script acts as a digital filter, instantly converting messy human conversation into a **clean JSON object** that you can pipe directly into **Jira**, **Trello**, or a **SQL database**.<\/p>\n
We leverage the **OpenAI API** combined with **Pydantic**, a data validation library. By using **Structured Outputs**, we force the LLM to adhere to a specific schema. This eliminates the common problem of the AI returning conversational fluff or incorrectly formatted text. We use **pathlib** for robust file handling to ensure the script works across **Windows**, **macOS**, and **Linux** without path errors.<\/p>\n
pip install openai pydantic python-dotenv<\/code><\/li>\n<\/ul>\nThe code<\/h2>\n\n\"\"\"\n-----------------------------------------------------------------------\nAuthors: Sharanam & Vaishali Shah\nRecipe: AI Transcript Structurer\nIntent: Extract validated JSON action items from raw meeting text.\n-----------------------------------------------------------------------\n\"\"\"\nimport json\nfrom pathlib import Path\nfrom typing import List\nfrom pydantic import BaseModel\nfrom openai import OpenAI\n\n# Define the data structure for validation\nclass ActionItem(BaseModel):\n task: str\n assignee: str\n priority: str\n\nclass MeetingSummary(BaseModel):\n decisions: List[str]\n action_items: List[ActionItem]\n sentiment: str\n\ndef extract_insights(file_path: str):\n # Initialize the client (ensure OPENAI_API_KEY is in your environment)\n client = OpenAI()\n \n # Read the transcript using pathlib\n target_file = Path(file_path)\n if not target_file.exists():\n print(f\"Error: {target_file} not found.\")\n return\n\n raw_text = target_file.read_text(encoding='utf-8')\n\n # Call the LLM with structured output response format\n completion = client.beta.chat.completions.parse(\n model='gpt-4o-2024-08-06',\n messages=[\n {'role': 'system', 'content': 'Extract structured insights from the meeting transcript.'},\n {'role': 'user', 'content': raw_text},\n ],\n response_format=MeetingSummary,\n )\n\n # Parse the validated response\n insights = completion.choices[0].message.parsed\n \n # Save the output as JSON\n output_file = target_file.with_suffix('.json')\n with open(output_file, 'w') as f:\n json.dump(insights.model_dump(), f, indent=4)\n \n print(f\"Success! Insights saved to {output_file}\")\n return insights\n\nif __name__ == '__main__':\n # Create a dummy transcript for demonstration\n temp_file = Path('transcript.txt')\n temp_file.write_text('Dave: We need to fix the login bug by Friday. Sarah, can you handle that? Sarah: Sure. We also decided to switch to Postgres for the database.')\n \n # Run the extraction\n extract_insights('transcript.txt')\n<\/code><\/pre>\nCode walkthrough<\/h2>\n
The script begins by defining a **Pydantic schema**. The **ActionItem** and **MeetingSummary** classes tell Python exactly what fields to expect from the AI. This is the **source of truth** for your data. We then use **Path** from the **pathlib** module to handle the file input, which is more reliable than the older **os.path** approach. <\/p>\n
The core logic happens in the **client.beta.chat.completions.parse** method. By passing our **MeetingSummary** class into the **response_format** parameter, we tell the **OpenAI API** to validate the response against our model before it even reaches our script. If the AI tries to skip a field, the request fails, ensuring you never receive **broken JSON**. Finally, we use **model_dump** to convert the Python object back into a standard dictionary and save it as a **formatted JSON file**.<\/p>\n
Sample output<\/h2>\n
When you run the script with the sample transcript, the terminal will display a success message, and a new file named **transcript.json** will appear in your directory with this content:<\/p>\n
\n{\n \"decisions\": [\n \"Switch to Postgres for the database\"\n ],\n \"action_items\": [\n {\n \"task\": \"Fix the login bug\",\n \"assignee\": \"Sarah\",\n \"priority\": \"High\"\n }\n ],\n \"sentiment\": \"Productive\"\n}\n<\/code><\/pre>\nConclusion<\/h2>\n
Automating meeting summaries is no longer about simple keyword matching. By combining **Python types** with **LLM intelligence**, you create a robust pipeline that understands context and enforces data integrity. This script provides a solid foundation for building larger automation tools, such as auto-filling **Jira tickets** or sending **Slack alerts** based on meeting outcomes. You can now process hundreds of transcripts in seconds, ensuring that no critical decision ever falls through the cracks again.<\/p>\n
\n\n\ud83d\ude80 Don’t Just Learn AI & LLMs \u2014 Master It.<\/h3>\n
\n This tutorial was just the tip of the iceberg. To truly advance your career and build professional-grade systems<\/strong>, you need the full architectural blueprint.\n <\/p>\n