Resources · n8n integration

AssemblyAI n8n integrationAutomate AssemblyAI with n8n.

Every recording sitting on a drive is text nobody has read yet. The AssemblyAI n8n integration turns audio and video into transcripts inside a workflow, with 12 operations spread over 3 resources, from uploading a file to pulling subtitles and running LLM Gateway prompts.

Community node This node is not shipped with n8n: it is a community package (n8n-nodes-assemblyai) you install from Settings › Community nodes on a self-hosted instance. npm

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the AssemblyAI n8n integration actually give you?

The AssemblyAI node calls a speech to text API from inside an n8n workflow. You point it at an audio or video file and get back a transcript, with the extras you asked for at creation time. The whole node fits in 3 resources: File handles the upload, Transcript covers the transcription and its derived views, LLM Gateway runs models over a transcript once it exists.

Take a team that records its sales calls. A workflow uploads the recording with Upload a file, starts a transcription with Speaker Labels turned on, then sends the finished text to the LLM Gateway with a short prompt asking for objections and next steps. The result lands as a row in Google Sheets, one line per call, searchable the same afternoon.

A podcast team has a different problem: captions. Create a transcription from the published audio URL, wait for it to finish, then call Get subtitles with Format set to srt and a cap on characters per caption. The file goes to storage and a message in Slack tells the editor the captions are ready before the episode goes live.

Support teams care about what is in the audio, not who said their card number. Turning on Redact PII and Redact PII Audio at creation gives both a masked transcript and a masked audio file, which Get redacted audio hands back as a URL. Only that version leaves the workflow, forwarded with Gmail to whoever reviews the call.

There is no AssemblyAI trigger node, so a workflow never starts with AssemblyAI. It starts with a Schedule Trigger running at a fixed interval, with an n8n Webhook, meaning a URL another service calls, or with the trigger of another tool. When an endpoint of the API has no matching operation here, the HTTP Request node covers it and reuses the same credential through predefined authentication.

Two limits are worth knowing before you build. Summarization, Summary Model, Summary Type and Auto Chapters are marked deprecated and will be removed later, so chapter and summary work belongs in Chat completion instead. And on List transcriptions, Limit caps how many transcripts come back, which is easy to forget when a run suddenly returns fewer items than expected. Our n8n review covers how the platform behaves once workflows like these pile up, and the n8n training walks through building one end to end.

Connect

How do you install and connect AssemblyAI in n8n?

  1. 01

    Install the community package

    This node does not come with n8n. Open Settings, go to Community nodes, and install the npm package n8n-nodes-assemblyai, currently version 0.4.0. That path exists on a self hosted instance, whether n8n runs through Docker or npm. On n8n Cloud, only verified community nodes can be installed, so check that status before planning around it. Once installed, AssemblyAI shows up in the node panel like any other.

  2. 02

    Create the credential once

    A credential in n8n is a saved set of connection details. You create it once from the Credentials menu and every workflow on the instance can reuse it, which means no copying keys between nodes. The AssemblyAI node has no authentication selector of its own: it simply offers the saved credential in its dropdown. Create it before you drop the first node, and the rest of the setup is picking it from a list.

  3. 03

    Run one transcription end to end

    Add the AssemblyAI node, pick the credential, choose the Transcript resource and the Create a transcription operation, then paste a public audio URL into Audio URL. Execute the node alone. You get back a transcript object with its ID. Copy that ID into a second node set to Get a transcription and confirm the text comes through. Two clean executions are enough to know the install and the credential both work.

Actions

What can the AssemblyAI node do?

The AssemblyAI node exposes 12 operations across 3 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceCreateGetDeleteChat CompletionGet ParagraphsGet Redacted AudioGet SentencesGet SubtitlesListSpeech UnderstandingUploadWord Search
File✓
LLM Gateway✓✓
Transcript✓✓✓✓✓✓✓✓✓

File

1 operation
01

Upload a file

file.upload

What you see in n8n

Notes & use cases

Sends a media file to AssemblyAI and returns a URL you can hand to a transcription. Use it whenever the audio is not already on a public address.

Key parameters

  • File Path or Binary Data: either a path to the file to upload, or the name of the binary property carrying it, typically data when the file arrives from a download node.
Use cases
a recording pulled from an internal drive, or a voice message downloaded earlier in the workflow, gets uploaded so the next node has something to point at.

LLM Gateway

2 operations
02

Chat completion

llm_gateway.chatCompletion

What you see in n8n

Notes & use cases

Sends a chat completion request to a language model through the AssemblyAI gateway, and returns the model output. This is where summaries, chapter lists and extraction live now.

Key parameters

  • Model: the model that answers, picked from a list that spans Claude, Gemini and GPT entries such as claude-sonnet-4-5-20250929 or gpt-5-mini.
  • Transcript ID: optional. When set, the first literal {{ transcript }} tag found in the messages or in the Prompt is swapped for the transcript text before the model runs.
  • Temperature and Max Tokens: how loose the wording gets, and how long the answer can run.
Use cases
a meeting transcript comes back as five bullet points and a list of owners, ready to post.
03

Speech understanding

llm_gateway.speechUnderstanding

What you see in n8n

Notes & use cases

Runs a speech understanding task over a transcript that already exists, and returns the processed result rather than a new transcription.

Key parameters

  • Transcript ID: the transcript to process, often {{ $json.id }} from the node that created it. Required, so an empty value stops the node.
  • Task Type: translation, speaker_identification or custom_formatting.
  • Target Languages: comma separated codes such as es,de.
  • Speaker Type: name or role, and it needs the transcript to have had Speaker Labels enabled.
Use cases
a webinar recorded in English comes back in Spanish and German for the local landing pages.

Transcript

9 operations
04

Create a transcription

transcript.create

What you see in n8n

Notes & use cases

Starts a new transcription from an audio address. Everything that shapes the output is decided here, in an Additional Fields collection holding 48 options.

Key parameters

  • Audio URL: the address of the audio to transcribe, usually the URL returned by Upload a file.
  • Speaker Labels: identifies who is speaking, and several later options depend on it.
  • Speech Models (Priority Order): a comma separated priority list such as universal-3-5-pro,universal-3-pro,universal-2. This is now the only way to choose a model.
  • Key Terms: domain vocabulary to raise accuracy, up to 1000 terms for Slam-1 and 200 for Universal.
Use cases
a legal team feeds in hearing recordings with case specific terms, so names and references come out spelled right.
05

Delete a transcription

transcript.delete

What you see in n8n

Notes & use cases

Removes a transcription from AssemblyAI. Nothing else in the workflow changes, so anything already written to a sheet or a message stays where it is.

Key parameters

  • Transcript ID: the ID of the transcript to remove, commonly stored in the same row that received the text earlier.
Use cases
a retention workflow runs on a schedule, collects transcripts older than the retention window and clears them once the text has been archived elsewhere.
06

Get a transcription

transcript.get

What you see in n8n

Notes & use cases

Fetches a transcription by its ID and returns the full object, text and status included. Since Create a transcription returns before the audio has been processed, this is the node that tells you whether the work is done.

Key parameters

  • Transcript ID: the ID of the transcript, usually carried from the create step as {{ $json.id }}.
Use cases
a Schedule Trigger checks pending transcripts every few minutes and pushes the ones that came back completed into the rest of the workflow.
07

Get paragraphs

transcript.getParagraphs

What you see in n8n

Notes & use cases

Returns the transcript split into paragraphs instead of one block of text. Useful when the raw transcript is too long to hand straight to anything downstream.

Key parameters

  • Transcript ID: the ID of the transcript whose paragraphs you want.
Use cases
an interview becomes a draft article, each paragraph mapped to a section before an editor rewrites the intro and the pull quotes.
08

Get redacted audio

transcript.getRedactedAudio

What you see in n8n

Notes & use cases

Returns the URL of the redacted audio file, the version where personal information has been masked in the sound itself.

Key parameters

  • Transcript ID: the ID of the transcript the redacted audio belongs to. The file only exists if Redact PII Audio was enabled back at Create a transcription, so ask for it there first.
Use cases
a call recording is shared with an outside quality reviewer, and the card numbers a customer read out loud never leave the building.
09

Get sentences

transcript.getSentences

What you see in n8n

Notes & use cases

Returns the transcript cut into sentences, a finer grain than paragraphs and a better unit when each piece needs its own timing.

Key parameters

  • Transcript ID: the ID of the transcript to break into sentences.
Use cases
a product demo gets an indexed table of contents, with each sentence stored as its own record so a search jumps straight to the moment it was said.
10

Get subtitles

transcript.getSubtitles

What you see in n8n

Notes & use cases

Returns ready to use subtitles for a finished transcription, in the caption format a player expects.

Key parameters

  • Transcript ID: the ID of the transcript to get subtitles for.
  • Format: srt or vtt, depending on what the player or the platform accepts.
  • Characters Per Caption: the maximum length of a single caption, which is how you stop lines from filling the screen.
Use cases
a training video is published with captions generated in the same run that produced its transcript, no manual timing pass.
11

List transcriptions

transcript.list

What you see in n8n

Notes & use cases

Lists the transcriptions on the account, with filters to narrow the batch before anything downstream touches it.

Key parameters

  • Limit: the maximum number of transcripts returned, so a run stays predictable instead of pulling the whole history.
  • Status: keeps only completed, error, processing or queued transcripts.
  • After ID and Before ID: paging markers to walk through the account without repeating items.
Use cases
a daily check pulls every transcript with the error status and raises them before anyone notices a missing summary.
12

Search words

transcript.wordSearch

What you see in n8n

Notes & use cases

Looks for specific words inside a transcript and returns where they appear, instead of handing back the whole text for something else to scan.

Key parameters

  • Transcript ID: the ID of the transcript to search.
  • Words to Search: either a comma separated string, or individual terms added one by one.
  • Input Type: picks between the comma separated list and the individual terms.
Use cases
a competitor name mentioned on a sales call flags the recording for review, without anyone listening to the full hour.
Need help

Need help automating AssemblyAI with n8n?

A person reads every message.

FAQ

AssemblyAI and n8n, the questions that come next

01Is the AssemblyAI n8n integration free?
There is no charge on the n8n side, but this one needs an install first. AssemblyAI is a community node, which means it does not ship with n8n: it is the npm package n8n-nodes-assemblyai, version 0.4.0, added from Settings and then Community nodes. That path is available on a self hosted instance, running through Docker or npm. On n8n Cloud, only verified community nodes can be installed, so confirm that status before you build a workflow around it. Once the package is on the instance, the node behaves like any other, and running it costs nothing extra in n8n itself.
02What credentials do you need to connect AssemblyAI to n8n?
One credential, created once. In n8n a credential is a saved set of connection details that lives on the instance rather than inside a single workflow, so every workflow can reuse it. The AssemblyAI node has no authentication selector of its own, so there is no method to pick: it simply offers the saved credential in its dropdown, and you select it. Create the credential from the Credentials menu before you add the first node, and the same entry then serves every AssemblyAI node on the instance. If you later add an HTTP Request node for an endpoint the node does not cover, it reuses that same credential through predefined authentication.
03What are the limits of the AssemblyAI node in n8n?
A few, and they are worth knowing early. The node exposes 12 operations over 3 resources, so anything outside that list goes through the HTTP Request node, which can call any endpoint of the API while reusing the same credential. Several options on Create a transcription are marked deprecated, including Summarization, Summary Model, Summary Type and Auto Chapters, with the LLM Gateway resource named as the replacement for summaries and chapters. On List transcriptions, Limit caps how many transcripts come back. And there is no trigger node here, so AssemblyAI cannot start a workflow on its own.
04Does AssemblyAI react in real time in n8n?
No, because there is no AssemblyAI trigger node. A workflow that uses AssemblyAI has to start somewhere else. Three routes are common. A Schedule Trigger runs the workflow at a fixed interval, which suits a batch of recordings collected overnight. An n8n Webhook, meaning a URL another service calls, lets an upload tool or a recorder kick the workflow off as soon as a file lands. Or the trigger of another tool starts it, a new message or a new row somewhere else. Create a transcription also offers a Webhook URL field, called when the transcription completes.
05n8n or Make for AssemblyAI?
It depends on where the audio can live and how you want to pay. Make is a hosted automation platform with no self hosting option, billed per operation, which keeps setup short and makes cost rise with volume. n8n runs on n8n Cloud or on your own infrastructure through Docker or npm, and the workflow is identical either way, so recordings and transcripts can stay on machines you control. That matters when calls contain personal data. The counterpoint is real: the AssemblyAI node is a community package, so on n8n it is one more thing to install and keep updated, and Make asks nothing of the sort.