# Descript integrations: media imports

> Import media from a URL, run an AI edit and publish project media in Descript, and start a workflow when Descript sends “Job completed”.

**Canonical page:** https://tray.ai/connectors/descript-integrations/
**Categories:** Design and creative
**Connects through:** HTTP Connector

## Overview

Descript is a video and podcast editor where you edit recordings by editing their transcript, with AI edits for captions, filler words, and audio cleanup. Tray.ai connects to Descript through the HTTP Connector, so your workflows can call the Descript API alongside the rest of your stack.

## Use cases

### Media imports

Create media imports in Descript from any Tray.ai workflow. The Descript API covers calls such as import media from a URL and import media into a project.

- Import media from a URL
- Import media into a project

### Agent edits

Read and create agent edits in Descript from any Tray.ai workflow. The Descript API covers calls such as run an AI edit and list agent models.

- Run an AI edit
- List agent models

### Projects

Read and create projects in Descript from any Tray.ai workflow. The Descript API covers calls such as list projects and get project details.

- List projects
- Get project details
- Publish project media

### Jobs

Read and delete jobs in Descript from any Tray.ai workflow. The Descript API covers calls such as list jobs and get job status.

- List jobs
- Get job status
- Cancel a job

### Drive search

Read drive search in Descript from any Tray.ai workflow. The Descript API covers calls such as search a drive and get published project metadata.

- Search a drive
- Get published project metadata

### Descript events

Start a Tray.ai workflow the moment something happens in Descript. Descript sends events such as job completed and job failed to a Tray.ai webhook trigger.

- Job completed
- Job failed

## Challenges Tray.ai solves

### Keeping Descript credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Descript credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Descript API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Descript API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Descript?

Yes. Tray.ai connects to Descript through the HTTP Connector, which calls the Descript API directly. Any call the Descript API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Descript?

The Descript API uses a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Descript connector?

Descript runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Descript connector from the Descript API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/