Gladia icon

CONNECT APP

Build with Gladia

Audio Intelligence API for companies.

Language Tools

  • API key

MCP

Give your agent Gladia tools

Every Gladia action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Gladia account for each tool call — you store no tokens.

// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
  new URL("https://remote.mcp.pipedream.net/v3"),
  {
    requestInit: {
      headers: {
        Authorization: `Bearer ${accessToken}`,
        "x-pd-project-id": "{project_id}",
        "x-pd-environment": "production",
        "x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
        "x-pd-app-slug": "gladia",
      },
    },
  },
)

const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)

const { tools } = await mcp.listTools()

// e.g. run Send Audio For Transcription:
const result = await mcp.callTool({
  name: "gladia-send-audio-for-transcription",
  arguments: {
    audio: "Audio File or URL",
    toggleNoiseReduction: true,
  },
})

API PROXY

Call the Gladia API directly

For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Gladia API with the connected user's credentials attached. You store no tokens and write no refresh logic.

const resp = await pd.proxy.get({
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  accountId: "apn_xxxxxxx",
  url: "https://api.gladia.io/audio/text/audio-transcription/",
})

// Any allowed Gladia endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.

SDK

Run Gladia actions from your backend

Connect a user's Gladia account once, then run Send Audio For Transcription on their behalf from your own code — TypeScript, Python, or plain HTTP.

import { PipedreamClient } from "@pipedream/sdk"

const pd = new PipedreamClient({
  projectId: process.env.PIPEDREAM_PROJECT_ID!,
  clientId: process.env.PIPEDREAM_CLIENT_ID!,
  clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
  projectEnvironment: "production",
})

const result = await pd.actions.run({
  id: "gladia-send-audio-for-transcription",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    gladia: { authProvisionId: "apn_xxxxxxx" },
    audio: "Audio File or URL",
    toggleNoiseReduction: true,
  },
})

EVENTS

Gladia triggers

Event sources your backend can deploy for users and receive through a webhook.

No Gladia triggers are available yet.

MULTI-APP

Use Gladia with other popular apps

Most products don't stop at one integration. Pair Gladia with the other apps your users rely on, and ship use cases that span both.

REFERENCE

App details

Reference metadata for the Gladia connector in the Pipedream registry.

App slug
gladia
Authentication
API key
Categories
Language Tools
Actions
1
Triggers
0
API proxy
Available