Turn live meetings into clear notes without typing. The flow listens to a meeting, captures the words, and stores them as clean text and action items. Teams can use it for sales calls, project reviews, and customer interviews.

Here is how it works. A setup path creates a meeting bot in Recall AI and opens an AI thread in OpenAI. The bot joins your call and sends live text to an n8n webhook. Each update is appended to a PostgreSQL record as a growing dialog list. A keyword check then passes only the new lines to an OpenAI assistant that keeps memory through a thread id. The assistant can call a database tool to write structured notes back into the same row. A Supabase record links the meeting url, bot id, and thread id so every item stays connected from start to finish.

Use it when you need reliable records and fast follow ups. You will need API keys for Recall AI and OpenAI plus access to a PostgreSQL database or Supabase. Expect to cut note work from about 30 minutes to under 5 minutes per meeting. Common uses include customer discovery, sales coaching, and internal reviews where action items must be captured while people speak.

• Webhook trigger receives live transcription updates from Recall AI
• HTTP request creates a meeting bot with a meeting url and a webhook destination
• OpenAI assistant thread is created and reused with a thread id for memory
• PostgreSQL query appends each transcript chunk to a dialog list for that meeting
• Keyword check routes only new lines for AI processing when a term is detected
• AI tool call writes structured notes back into the same database record
• Supabase record stores meeting url bot id and thread id for easy tracking

• Reduce manual note work from 30 minutes to under 5 minutes per meeting
• Automate most transcription and note capture so people can focus on the call
• Improve action item accuracy by logging notes as they are said
• Connect Recall AI OpenAI Supabase and PostgreSQL in one flow
• Scale to many meetings without adding extra staff
• Keep one source of truth with linked bot id and thread id per meeting

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Recall.ai, OpenAI, Supabase and PostgreSQL. See the Tools Required section above for links to create accounts with these services.
3. In the n8n credentials manager, open the node named Create Recall bot. In the credential dropdown choose Create new credential. Select HTTP Header Auth, name it Recall, and paste your Recall API key from the Recall dashboard. Save the credential.
4. Open the node named Create OpenAI thread. In the credential dropdown choose Create new credential. Select OpenAI API Key, name it clearly, and paste your OpenAI API key from the OpenAI API page. Save the credential.
5. Prepare your database. In Supabase create a table named data with id, date_created, input as JSONB, and output as JSONB. If you prefer a direct PostgreSQL instance, create the same fields there as well.
6. In n8n, set up the PostgreSQL credential used by Insert Transcription Part and Create Note. Double click each node, choose Create new credential, enter host, database, user, password, and SSL if required. Test the connection and save.
7. Open the node Scenario 1 Start Edit Fields and enter your meeting url and your server domain. These values are used to create the bot and route live text to your n8n webhook.
8. Open the node Create Recall bot and confirm the destination url points to the Webhook node named Scenario 2 Start Webhook. If you are on n8n Cloud, copy the exact production webhook url and paste it here.
9. Open the node Create OpenAI thread and confirm the assistants v2 header is present. Make sure the OpenAI credential you created is selected.
10. Run the Scenario 1 path once to create the Recall bot and the OpenAI thread. Then check your Supabase data table and confirm a new row exists with the meeting url, bot id, and thread id.
11. Start a test meeting and speak for a minute. Say the keyword Jimmy to trigger note creation. Review your PostgreSQL record and confirm output dialog and output notes lists are being updated.
12. Troubleshooting tips. If the Webhook node shows no hits, verify the destination url in Create Recall bot. If Recall returns 401, recheck the API key. If OpenAI errors, confirm the assistants version header and your key. If database writes fail, confirm the table fields and user permissions.