How to use OpenAI node with gpt-4o-transcribe-diarize model?

Describe the problem/error/question

I want to include a node that transcribes an mp3 file with diarization.

I’ve tried to use the OpenAI node “transcribe a recording“ (which relies on Whisper) but it doesn’t do diarization.

So I’ve tried to use OpenAI node “gpt-4o-transcribe-diarize” model but I can’t pass the mp3 file as input with this model. I try to put “data” in the user prompt but it doesn’t work.

But how can I set the mp3 file as the input? When I use OpenAI-transcribe node (Whisper), it takes the mp3 file as input data ; but when I use AI Agent+OpenAI (configured with the model gpt-4o-transcribe-diarize), I just can’t define the binary data as the input.

Thanks for your help!

What is the error message (if any)?

When I put "data” in the user prompt:

The service was not able to process your request. The server had an error while processing your request. Sorry about that!

Which is understandable since it doens’t include the binary input file.

Please share your workflow

Share the output returned by the last node

{
“errorMessage”: “The service was not able to process your request”,
“errorDescription”: “The server had an error while processing your request. Sorry about that!”,
“errorDetails”: {
“rawErrorMessage”: [
“500 The server had an error while processing your request. Sorry about that!”
]
},
“n8nDetails”: {
“nodeName”: “AI Agent1”,
“nodeType”: “@n8n/n8n-nodes-langchain.agent”,
“nodeVersion”: 3,
“time”: “30/01/2026, 09:52:40”,
“n8nVersion”: “1.123.9 (Cloud)”,
“binaryDataMode”: “filesystem”,
“stackTrace”: [
“NodeOperationError: The service was not able to process your request”,
" at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/@n8n+n8n-nodes-langchain@file+packages+@n8n+nodes-langchain_9a205f921775d8d377839c435a485ccb/node_modules/@n8n/n8n-nodes-langchain/nodes/agents/Agent/agents/ToolsAgent/V3/helpers/executeBatch.ts:88:11",
" at Array.forEach ()“,
" at executeBatch (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/@n8n+n8n-nodes-langchain@file+packages+@n8n+nodes-langchain_9a205f921775d8d377839c435a485ccb/node_modules/@n8n/n8n-nodes-langchain/nodes/agents/Agent/agents/ToolsAgent/V3/helpers/executeBatch.ts:77:15)”,
" at processTicksAndRejections (node:internal/process/task_queues:105:5)“,
" at ExecuteContext.toolsAgentExecute (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/@n8n+n8n-nodes-langchain@file+packages+@n8n+nodes-langchain_9a205f921775d8d377839c435a485ccb/node_modules/@n8n/n8n-nodes-langchain/nodes/agents/Agent/agents/ToolsAgent/V3/execute.ts:49:66)”,
" at ExecuteContext.execute (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/@n8n+n8n-nodes-langchain@file+packages+@n8n+nodes-langchain_9a205f921775d8d377839c435a485ccb/node_modules/@n8n/n8n-nodes-langchain/nodes/agents/Agent/V3/AgentV3.node.ts:131:10)“,
" at WorkflowExecute.executeNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_ec37920eb95917b28efaa783206b20f3/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1045:8)”,
" at WorkflowExecute.runNode (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_ec37920eb95917b28efaa783206b20f3/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1226:11)“,
" at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_ec37920eb95917b28efaa783206b20f3/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:1662:27”,
" at /usr/local/lib/node_modules/n8n/node_modules/.pnpm/n8n-core@file+packages+core_@[email protected]_@[email protected]_ec37920eb95917b28efaa783206b20f3/node_modules/n8n-core/src/execution-engine/workflow-execute.ts:2274:11"
]
}
}

Information on your n8n setup

  • n8n version: 1.123.9 (Cloud)
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app): n8n cloud
  • Operating system: n8n cloud

Hi @Ravage9252, welcome!

There is no model selection in the built-in OpenAI “Transcribe a recording” node, and you can’t use the AI Agent for that, as shown in your workflow.

The solution is to call the endpoint directly using an HTTP request:
https://platform.openai.com/docs/api-reference/audio/createTranscription
Here’s an example:

3 Likes

Hi @Ravage9252

Just to clarify
AI agent node only sends text prompts, so writing data in the prompt doesn’t send de mp3 file, and the model fails because it expects real audio binary input. To use gpt4, you need to call the openAI audio directly (like mohamed3nan says) and send the mp3 as a file instead of text.

Hope this helps.

2 Likes

Thank you.

Is there any plan to include the model selection for the “Transcribe a recording” OpenAI node?
It would be nice to choose between all OpenAI models: whisper, gpt-4o-transcribe and gpt-4o-transcribe-diarize.

2 Likes

Totally with you on this, I think n8n will eventually add it, especially as they keep improving the nodes..

1 Like

As a side node - ‘n8n-nodes-transcribe-com’ community node can be used to convert audio into transcription with speaker diarization, afaik transcribe.com transcribation works better than OpenAI’s models in many cases

1 Like

Thanks!
Good to know.

I’m gonna try this node

Is it possible to install this node with n8n Cloud instance (n8n plan)?

I can’t find the option to install a node.

HI @Ravage9252! On n8n Cloud it can be a bit confusing at first, but community or custom nodes cannot be installed there. Those nodes are only supported on self hosted setups like Docker, npm, or the desktop app. For your case, the usual alternative is to use the HTTP Request node or native nodes that provide similar functionality.

Not yet, there is a problem with current n8n codebase that prevents new nodes to be submitted for approval. Issue filed, but n8n team did not fix it as of now: n8n-node release: lint error preventing node publishing · Issue #25190 · n8n-io/n8n · GitHub

Until fix many nodes (including this one) simply impossible to submit to n8n for n8n Cloud availability :man_shrugging:

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.