npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

n8n-nodes-gladia

v0.1.1

Published

Gladia dedicated nodes for n8n

Readme

Gladia n8n Custom Nodes

Gladia n8n Custom Nodes

This repository contains custom n8n nodes built by Gladia to integrate Gladia’s APIs and internal tools directly into n8n.
These nodes let you automate workflows that use Gladia’s services — such as transcription, embeddings, and audio intelligence — seamlessly inside n8n.

To use these nodes, you’ll need a Gladia API key. You can generate one for free by creating an account at app.gladia.io.

Once logged in, go to your dashboard and copy your personal API key — you’ll need to add it in n8n when configuring any Gladia node.

For more information about Gladia’s APIs, visit the official documentation.


Local Installation

To use the Gladia n8n custom nodes locally, follow these steps:

  1. Make sure n8n is installed globally

    npm install -g n8n
  2. Navigate to n8n’s local nodes directory

    cd ~/.n8n/nodes
  3. Install the Gladia package

    npm install n8n-nodes-gladia
  4. Start n8n

    n8n start

Available Nodes

This package provides three nodes to interact with Gladia’s Speech-to-Text (STT) API and retrieve transcription results from audio files.

1. File Upload

The File Upload node lets you upload an audio file to Gladia.
This step is required if your audio file isn’t publicly accessible (e.g., stored locally or behind authentication).
It sends the audio file’s binary data to Gladia, where it’s securely stored, and returns a file URL.

That URL will be used in the next step.

Input:

  • Audio file (binary data)

Output:

  • File URL (used by the Start Transcription node)

2. Start Transcription

The Start Transcription node sends the audio URL to Gladia to start the transcription process.
You can include various optional parameters to improve accuracy or customize output:

  • audio_language — specify the spoken language
  • custom_vocabulary — provide a list of domain-specific terms
  • custom_spelling — define preferred spellings or formatting
  • Other options supported by the Gladia API

Input:

  • Audio file URL (from File Upload or a public URL)

Output:

  • Transcription request ID and metadata

3. Get Transcription

The Get Transcription node retrieves the full transcription data from Gladia.
It performs a simple GET request using the transcription ID obtained in the previous step.

Input:

  • Transcription request ID

Output:

  • Full transcription text
  • Confidence scores
  • Summarization, chapterization, etc.

Example Flow

A typical workflow might look like this:

  1. File Upload → Upload local file and get URL
  2. Start Transcription → Send file URL to start transcription
  3. Get Transcription → Retrieve transcription results once complete

If your file is already public (e.g., hosted on an accessible URL), you can skip the File Upload node and start directly from Start Transcription.