The AssemblyAI n8n Integration

Unlock the full potential of AssemblyAI and n8n’s automation platform by connecting AssemblyAI’s speech-to-text and audio intelligence capabilities with over 1,000 apps, data sources, services, and n8n’s built-in AI features.

The AssemblyAI n8n integration is built and maintained by AssemblyAI (verified by n8n).

Overview

This comprehensive tutorial walks you through building a complete AssemblyAI workflow within n8n Cloud that:

1. Watches for changes to a Google Drive folder
2. Once an audio file is added, submits a transcription request to AssemblyAI with the audio
3. Polls for the transcription process to complete
4. Once complete, processes the transcript into a text file with just the transcript text and speaker labels
5. Saves the processed transcript .txt file output to a Google Drive folder
6. Deletes the transcript from AssemblyAI’s servers

Prerequisites

Before you begin, you’ll need:

• An AssemblyAI API key
  • Signing up for an AssemblyAI account is free! An account on the free tier can transcribe up to $50 in transcription and will be able to process up to five files concurrently. If you upgrade your account before using $50 in transcription any unused amount will be retained on your account.
• An n8n account, either via n8n Cloud (recommended) or a self-hosted instance.
• A Google Cloud account for Google Drive API access
  • A folder in Google Drive to monitor for new audio files (/audio_files)
  • A folder in Google Drive to save the formatted .txt transcript output (/transcripts)

Credentials

Before building your workflow, you’ll need to configure credentials for both Google Drive and AssemblyAI in n8n.

Google Drive OAuth Credentials

1. Go to your n8n credentials page
2. Click Add Credential and search for “Google Drive OAuth2 API”
3. Follow the setup process to connect your Google Drive account with Google Cloud Console:
   • Video tutorial: Setting up Google Drive credentials
   • n8n documentation: Google OAuth setup
4. Save the credential

AssemblyAI Credentials

1. Go to your n8n credentials page
2. Click Add Credential and search for “AssemblyAI API”
3. Enter your AssemblyAI API key
4. Save the credential

Once both credentials are configured, you can use them throughout your workflow.

Instructions

Step 1: Set Up Your Workflow and Trigger

1

Create a new workflow on n8n

1. Log in to your n8n account (either n8n Cloud or your self-hosted instance)
2. Click the + icon or New Workflow to create a new workflow
3. Give your workflow a descriptive name (e.g., “AssemblyAI Transcription Pipeline”)
4. Install the AssemblyAI node:
   • Click the + icon to open the nodes panel
   • Search for “AssemblyAI”
   • Click the Install button next to the AssemblyAI node

2

Choose Your Trigger

The first step is to decide how n8n will know when your audio file is ready to transcribe. This is your workflow trigger. For this example, we’ll use Google Drive to automatically trigger the workflow when a new audio file is added to a folder.

1. Link your Google Drive account with the credentials you created in the Credentials step.
2. Add a Google Drive trigger node to your workflow
3. Select the trigger event: On changes involving a specific folder
4. Configure the trigger parameters:
   • Credential to connect with: Select your Google Drive credentials
   • Poll Times: Set Mode to Every Minute
   • Trigger On: Changes Involving a Specific Folder
   • Folder: From list + Select the folder in Google Drive to monitor
   • Watch For: File Created

When a new audio file is added to the specified Google Drive folder, the workflow will run.

Running the workflow

To test the workflow, you can manually trigger it at any time by clicking the orange Execute Workflow button in the n8n editor to populate the nodes with sample data.

For the Google Drive trigger to work as intended, you will need to deploy this workflow (to n8n cloud) and then add a new audio file to the monitored folder in Google Drive (/audio_files). This is handled in a later step.

For more information on supported audio file types, size limits, and using Google Drive with AssemblyAI, see:

• Can I submit files stored in Google Drive?
• What Is the Recommended File Type for Using Your API?
• What types of audio URLs can I use with the API?
• Are there any limits on file size or duration?

Important Google Drive Considerations

For the sake of simplicity, this tutorial uses a public Google Drive link, so you must ensure your file is 100 MB or less and the Google Drive folder settings are set to Public (anyone with the link can view).

If you’d like to transcribe private folders/files greater than 100MB, you’ll need to add a Google Drive “Download file” node to download the binary data first, then upload it to AssemblyAI using the AssemblyAI “Upload a file” node.

Step 2: Upload Audio File (Optional)

After the Google Drive trigger fires, you have the file’s webContentLink available at {{ $json.webContentLink }}.

For files under 100MB

You can skip this step and use the public Google Drive link directly in Step 3 without uploading. AssemblyAI accepts all Google Drive files below 100MB.

For files over 100MB

Use the AssemblyAI Upload node:

1. Add a Google Drive “Download File” node and configure it to download the file by ID (you can get the file ID from the trigger response)
2. Add an AssemblyAI “Upload a file” node
3. Configure the credential with your AssemblyAI API key
4. The upload will return an upload_url to use in the next step

Step 3: Submit Transcription Request

Now submit the transcription request with your desired features enabled.

1

Add the transcription (create) node

Using the + sign linked to the Google Drive trigger, add an AssemblyAI Create a transcription node.

2

Configure the node parameters

• Credential to connect with: Select your AssemblyAI Account credential (if you haven’t set this up yet, see Credentials)
• Resource: Transcript
• Operation: Create
• Audio URL: {{ $json.webContentLink }}
  • You can also drag and drop the webContentLink field from the Google Drive Trigger response into this field

3

Enable features

In Additional Fields, enable the following features for this tutorial:

• Speaker Labels: true (identifies different speakers through diarization)
• Language Detection: true (automatically detects the language, also known as ALD)

You can explore all available features, such as sentiment analysis, entity detection, pii redaction, and more in our API Reference.

The response will contain a transcript_id that you’ll use to poll for completion.

Step 4: Poll for Transcription Completion

Since transcription is asynchronous, the transcription request returns immediately. You need to poll the API until the transcript is ready.

1

Add a Wait node

Add a Wait node and configure the wait parameters:

• Resume: After Time Interval
• Wait Amount: 3.00
• Wait Unit: Seconds

This will wait 3 seconds before checking the transcript’s status.

2

Add the transcription (get) node

Add an AssemblyAI Get a transcription node after the Wait node and configure the node parameters:

• Credential to connect with: Select your AssemblyAI Account credential (see Credentials)
• Resource: Transcript
• Operation: Get
• Transcript ID: {{ $json.id }}
  • You can drag and drop the id field from the Create a transcription response into this field

3

Add a Switch node

Add a Switch node after the Get a transcription node and configure the switch to check the transcript’s status:

Add 4 routing rules, each with:

• Value 1: {{ $json.status }}
  • Or drag the status field from the Get a transcription response
• Condition: “is equal to”
• Value 2: Set one of these for each rule:
  1. queued
  2. processing
  3. error
  4. completed

4

Handle switch outputs

Handle each switch node output based on the transcript status:

• Output 0 (queued): Connect back to the Wait node to continue polling
• Output 1 (processing): Connect back to the Wait node to continue polling
• Output 2 (error): Add a Stop and Error node to halt the workflow
  • Note: You may want to add logging or resubmit the transcript instead
• Output 3 (completed): Continue to the next step to process the completed transcript

By connecting the processing and queued outputs back to the Get a transcription, you create a polling loop that continues checking (every 3 seconds) until the transcript is complete or encounters an error.

When the transcript is complete, the response will contain the full transcript data.

Step 5: Process Transcript Output into a Human-Readable Transcript

Once you have the completed transcript, we want to manipulate the data into a more usable format.

To pull out the transcript text with speaker labels:

1
transcript = _('Get a transcription').first().json
2
formatted_text = ''
3
4
if 'utterances' in transcript and transcript['utterances']:
5
    # Format with speaker labels
6
    for utterance in transcript['utterances']:
7
        formatted_text += f"Speaker {utterance['speaker']}: {utterance['text']}\n\n"
8
else:
9
    # Use plain text if no speaker labels
10
    formatted_text = transcript['text']
11
12
return {'formattedText': formatted_text}

Step 6: Save to Google Drive

To save the formatted transcript back to Google Drive:

1

Add a Convert to File node

Add a Convert to File node and configure it:

• Operation: Convert to Text File
• Text Input Field: formattedText
• Put Output File in Field: data

2

Add a Google Drive Upload file node

Add a Google Drive Upload file node and configure it:

• Credential to connect with: Select your Google Drive credential
• Resource: File
• Operation: Upload
• Input Data Field Name: data
• File Name: {{ $('Get a transcription').item.json.id }} (or drag and drop from input data)
• Parent Drive: From list > My Drive
• Parent Folder: From list > transcripts

The formatted transcript will be saved as a .txt file in your specified Google Drive folder:

Step 7: Delete Transcript (Optional)

Once you’re done processing the transcript, as it is now saved in Google Drive, you can optionally delete it from AssemblyAI’s servers.

The transcript will be permanently deleted from AssemblyAI’s servers.

Step 8: Deploy

Once the transcript has been deleted, the workflow is complete! At this point, it should look like this:

Now you can deploy the workflow to n8n Cloud by navigating back to the n8n Cloud Overview page, locating your workflow, and moving the slider icon to the Active position.

And we’re done! Add a file to /audio_files in Google Drive, and within a few seconds to a few minutes (depending on the Poll Times set for the Google Drive trigger and the duration of the audio file), you should see the transcript appear in the /transcripts Google Drive folder.

Conclusion

In this tutorial, you built a complete AssemblyAI transcription workflow in n8n that automatically processes audio files from Google Drive, submits them to AssemblyAI for transcription, polls for completion, formats the transcript with speaker labels, saves the output back to Google Drive as a .txt file, and finally deletes the transcript from AssemblyAI’s servers.

This is just one simple idea, but the possibilities are endless! You can customize this workflow further by adding additional AssemblyAI features and products like sentiment analysis, entity detection, and LLM Gateway (see the “What can you do with AssemblyAI?” section of this page for all available actions), or by integrating with other services like Slack, OpenAI, Supabase, Discord, and the hundreds of other official n8n integrations.

Additional Resources

• AssemblyAI n8n Integration Page
• AssemblyAI n8n Integration GitHub Repo

Need some help?

If you get stuck, think something is broken or missing from our n8n integration, or just have some questions, we’d love to help you out! Contact our support team directly via support@assemblyai.com or open a support ticket.