Gladia integration

Quick start

Call Gladia from your generated app's worker code via the OverSkill composio client. The toolkit slug below maps to Gladia's public Composio identifier — your app references it by name and OverSkill handles the OAuth round-trip.

// In your generated app's worker handler:
const composio = composioClient(env);

const result = await composio.execute(
  "GLADIA_ACTION_NAME",
  { /* action parameters — see Actions section below */ }
);

return new Response(JSON.stringify(result), {
  headers: { "Content-Type": "application/json" }
});

Replace ACTION_NAME with one of the slugs listed in the Actions section below. The composio client handles auth + rate limits automatically — no API key is exposed to user code.

Setup

End-users supply their own Gladia API key. OverSkill provides a pre-built connection form via the integration card — your app can call the composio client immediately once the user has connected.

Available actions

10 actions exposed via the Gladia integration. Each maps to a callable slug — pass it to composio.execute(...) in your worker code.

• GLADIA_DELETE_LIVE_SESSION
• GLADIA_DELETE_PRE_RECORDED_JOB
• GLADIA_GET_LIVE_TRANSCRIPTION_RESULT
• GLADIA_GET_PRE_RECORDED_JOB
• GLADIA_GET_TRANSCRIPTION_AUDIO_FILE_DEPRECATED
• GLADIA_INITIATE_LIVE_SESSION
• GLADIA_INITIATE_PRE_RECORDED_TRANSCRIPTION
• GLADIA_LIST_LIVE_TRANSCRIPTIONS
• GLADIA_LIST_PRE_RECORDED_JOBS
• GLADIA_UPLOAD_AUDIO_VIDEO_FILE