AI Agent for realtime insights on meetings — AI Product | Success.
AI Agent for realtime insights on meetings
AI Agent for realtime insights on meetings — free, ready-to-import n8n workflow (19 nodes, AI and LLMs).
AI ProductReusable license
from $0
Workflow Intelligence
Understand this workflow before you use it.
Full structure
1 to review
Health 82/100
Full workflow structure analyzed
Every step's connections are present in the source file, so the flow, paths and structure below reflect the real workflow.
This workflow starts from Webhook and works with AI text processing and a database.
Steps
9
Integrations
3
Connections
6
Complexity
Intermediate
Technical health
82/100
Security
1 to review
OpenAI
PostgreSQL
Supabase
Overview
**AI Agent for realtime insights on meetings**
Category: AI and LLMs · 19 nodes
Nodes/integrations used: httpRequest, openAi, postgres, postgresTool, supabase, webhook
How to use: download the JSON below, then in n8n choose Import from File (or open the demo link, copy the JSON, and paste with Ctrl+V into the n8n canvas). Add your own credentials and activate.
Source: enescingoz/awesome-n8n-templates (CC-BY-4.0). Credentials were removed and files modified for redistribution — see the library's ATTRIBUTION_AND_LICENSES.md for full license text.
After you purchase
Every downloadable file is security-scanned before it becomes available to you — files stay locked until that check passes.
Delivery is via short-lived, authenticated download links issued only after your purchase is confirmed — never a public file address.
Arrows are real connections from the workflow file. Dashed lines attach AI components (models, memory, tools) to the step that uses them.
Select a step to see what it is and how it fits in.
Security1 note(s) to review
0 Critical
0 High
1 Medium
0 Low
0 Info
MediumWebhook accepts unauthenticated requests
Anyone who learns the webhook URL can trigger this workflow with arbitrary data.
Confidence: medium · Heuristic
Suggested fix: Enable header or basic auth on the Webhook node, or verify a signature from the sending service.
HealthHow the technical score is made up
Overall 82/100.
Security90/100
−10: Webhook accepts unauthenticated requests
Structural75/100
−25: Nodes unreachable from any trigger
Data flow80/100
−10: Reference to a node that does not exist
−10: Reference to a node that does not exist
Error handling40/100
−60: No error handling around external calls
Maintainability100/100
Integration risk100/100
Execution complexity100/100
Technical hygiene signals detected statically from the workflow file. Not a guarantee of correctness or fitness for a particular use.
Execution profileWhat one run touches
Starts from: Webhook
HTTP requests
2
AI model calls
1
Database operations
2
OpenAI · model set at runtime
Cost
Pricing unavailable
Model usage is shown above; no price estimate is made.
Simulation
Safe simulation available
A mock walk-through with placeholder data. Nothing real is run or contacted.
DocumentationGenerated from the workflow's structure
What it does
This workflow starts from Webhook and works with AI text processing and a database.
Services involved: OpenAI, PostgreSQL and Supabase.
This description is generated from the workflow's node types and wiring. It does not interpret each node's configuration.
Inputs
Data enters through the trigger(s) below.
Some steps read fields from the incoming request body, query or headers.
Scenario 2 Start - Webhook (Webhook)
Main flow
The longest path runs through 4 steps:
Scenario 1 Start - Edit Fields (Set)
Create Recall bot (HTTP Request)
Create OpenAI thread (HTTP Request)
Create data record (Supabase)
Outputs
Create data record (Supabase)
Requirements
No credentials are attached in this file. You will need your own n8n credentials for each service below.
OpenAI
PostgreSQL
Supabase
Setup
Import the JSON file into n8n (Workflows → Import from File).
Create credentials for each service and select them on the matching nodes.
Run it once manually with test data before activating.
Important considerations
No node is configured to retry or continue on failure.
There is no Error Trigger in this workflow.
No error handling around external calls
Generated automatically from the workflow's structure. Verify behaviour in n8n before relying on it.
Optimization ideasAdvisory suggestions
Potential optimization · medium confidence
Independent HTTP requests run one after the other
"Create OpenAI thread" runs after "Create Recall bot" but none of its parameters reference "Create Recall bot"'s output.
Possible impact: Potential latency reduction if run in parallel branches.
"Create OpenAI thread" may still depend on "Create Recall bot" through side effects (e.g. "Create Recall bot" creates a record "Create OpenAI thread" then reads), which static analysis cannot see.
Automated static analysis (engine 1.1.0). Nothing was executed. Not a guarantee of correctness or safety.
The seller has not attached downloadable files yet.
Uploaded by the seller and security-scanned before any buyer can download them.
