Replace API key in Header, webhook from 2nd scenario, change settings if needed

Replace this link with direct link on your audio

Replace API key and webhook

Replace OpenAI connection

Scenario 1: Transcribe Call with AssemblyAI

1. Set Up Request:
   • Header Authentication: Set Authorization with AssemblyAI API key.
   • URL: POST to https://api.assemblyai.com/v2/transcript/.
   • Parameters:
     • audio_url: Direct URL of the audio file.
     • webhook_url: URL for an N8N webhook to receive the transcription result.
     • Additional Settings:
       • speaker_labels (true/false): Enables speaker diarization.
       • speakers_expected: Specify expected number of speakers.
       • language_code: Set language (default: en_us).

Scenario 2: Process Transcription with OpenAI

1. Webhook Configuration: Set up a POST webhook to receive AssemblyAI’s transcription data.

2. Get Transcription:

   • Header Authentication: Set Authorization with AssemblyAI API key.
   • URL: GET https://api.assemblyai.com/v2/transcript/<transcript_id>.

3. Send to OpenAI:

   • URL: POST to https://api.openai.com/v1/chat/completions.
   • Header Authentication: Set Authorization with OpenAI API key.
   • Body Parameters:
     • Model: Use gpt-4o-2024-08-06 for JSON Schema support, or gpt-4o-mini for a less costly option.
     • Messages:
       • system: Contains the main analysis prompt.
       • user: Combined speakers’ utterances to analyze in text format.
     • Response Format:
       • type: json_schema.
       • json_schema: JSON schema for structured responses.

4. Save Results in Supabase:

   • Operation: Create a new record.
   • Table Name: demo_calls.
   • Fields:
     • Input: Transcription text, audio URL, and transcription ID.
     • Output: Parsed JSON response from OpenAI’s analysis.

Call analyzer with AssemblyAI transcription and OpenAI assistant integration

Made by Mark Shcherbakov from community 5minAI

Many follow-up sales calls lack structured analysis, making it challenging to identify client needs, gauge interest levels, or uncover upsell opportunities. This workflow enables automated call transcription and AI-driven analysis to generate actionable insights, helping teams improve sales performance, refine client communication, and streamline upselling strategies.

This workflow transcribes and analyzes sales calls using AssemblyAI, OpenAI, and Supabase to store structured data. The workflow processes recorded calls as follows:

1. Transcribe Call with AssemblyAI: Converts audio into text with speaker labels for clarity.
2. Analyze Transcription with OpenAI: Using a predefined JSON schema, OpenAI analyzes the transcription to extract metrics like client intent, interest score, upsell opportunities, and more.
3. Store and Access Results in Supabase: Stores both transcription and analysis data in a Supabase database for further use and display in interfaces.

... or watch set up video [5 min]

Replace prompt and JSON schema

If you change speaker_labels to false it will require change user message in OpenAI and Supabase nodes

Replace Supabase connection

Scenario 1: Transcribe Call with AssemblyAI

Purpose and structure

This folder contains the Scenario 1: Transcribe Call with AssemblyAI workflow. Its executable nodes use httpRequest, if, manualTrigger, set, supabase, webhook. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

When clicking ‘Test workflow’, Webhook

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Webhook/0632_Webhook_Manual_Create_Webhook.json MIT; preserve source notices.