Templates / Extract post-call glossary terms from transcripts with Anthropic Claude and Telegram

Extract post-call glossary terms from transcripts with Anthropic Claude and Telegram

Needs changes

by Marco Venturi ✓ · 4 views · created 2026-06-24 · Document Extraction, AI Summarization

Needs changes. This template uses 1 thing(s) that n8n 3.0 removes: AI Agent v1 (old agent modes). 1 breaking item(s) found. Static check, last run 2026-10-19.

What this workflow does

This AI workflow has 11 nodes and runs when someone submits an n8n form (“Post-Call Glossary Extractor”) (plus 1 other trigger). Along the way it connects Anthropic Chat Model and Telegram.

How it runs

Trigger: When someone submits an n8n form (“Post-Call Glossary Extractor”) (plus 1 other trigger).

  1. Normalize: Form Input (Edit Fields (Set)): sets 2 fields: transcript, sessionId
  2. Normalize: Webhook Input (Edit Fields (Set)): sets 2 fields: transcript, sessionId
  3. AI Agent: runs an AI agent, with model: Anthropic Chat Model
  4. Extract JSON (Code): runs custom JavaScript code
  5. Any Terms Found? (If): checks a condition and branches into true / false
  6. Format Glossary Message (Code): runs custom JavaScript code
  7. KO - Send to Telegram (Telegram): uses Telegram
  8. OK - Send to Telegram (Telegram): uses Telegram

Services it uses

Anthropic Chat ModelTelegram

Before you upgrade to n8n 3.0

1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:

  • AI Agent v1 (old agent modes) in AI Agent (v1.7): replace with Latest AI Agent node (Tools Agent). For SQL Agent, use a Postgres or MySQL tool with a recent AI Agent.

Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).

Removed in 3.0Replace with
AI Agent v1 (old agent modes)
AI Agent (v1.7)
Latest AI Agent node (Tools Agent). For SQL Agent, use a Postgres or MySQL tool with a recent AI Agent.

Nodes used (8)

From the author

Quick overview This workflow accepts a meeting transcript via an n8n form or webhook, uses Anthropic Claude to extract technical terms and acronyms into a JSON glossary, and then sends either the formatted glossary or a “nothing to add” confirmation to…

Excerpt from Marco Venturi's description on n8n.io.

View the original on n8n.io → Check your own copy

Get the weekly “what broke” email

New templates, newly broken ones, and n8n release changes. One short email a week.

Form not loading? Subscribe here.