Skip to main content
A workflow that downloads a video or pulls a transcript often works in a test run and then fails on n8n Cloud or a VPS, because sites block datacenter IPs and many videos have no captions. Your workflow can send the link to Importly with n8n’s built-in HTTP Request node and get the transcript, file or metadata back. No community node or code is needed.

1. Add your key as a credential

Create your key on the API key page (it is shown once). In n8n, open Credentials, create a Header Auth credential and set: Every HTTP Request node below uses Authentication: Generic Credential Type, Generic Auth Type: Header Auth, and this credential. The key stays out of the workflow JSON, so you can share or export the workflow safely.

2. Get a transcript in one node

Add an HTTP Request node after your trigger (a form, a schedule, a new row in a sheet):
JSON body
To take the link from the previous node, replace the URL with an expression such as {{ $json.videoUrl }}. "mode": "auto" uses the video’s captions and falls back to speech-to-text when it has none. "wait": true holds the request open for up to 30 seconds, so a caption transcript usually comes back in this node’s output: If status is still running (long videos transcribed from audio), finish it with the polling loop in step 3, using GET https://api.importly.io/transcribe/status?id=.... A caption transcript costs $0.003; see Pricing & credits.

3. Import a file

POST /import starts a download and returns a jobId right away. Collect the file with an n8n Webhook node, or poll until it’s done.
Make a second workflow that starts with a Webhook node (HTTP Method POST) and activate it. Copy its Production URL. It must be a public https:// address, so this works on n8n Cloud or a self-hosted n8n behind a domain, not on localhost.In the first workflow, add an HTTP Request node: POST https://api.importly.io/import with this JSON body:
JSON body
When the job finishes, Importly sends one POST to the Webhook node. The result fields sit directly on data, so in the nodes after it the file link is {{ $json.body.data.mediaUrl }} and the title is {{ $json.body.data.title }}. A failed job arrives with success: false and a message (Failed jobs), so add an IF node on {{ $json.body.success }}.
mediaUrl is a signed link that expires after 7 days. To keep the file, add an HTTP Request node that downloads it (Response Format: File) and an upload node for Google Drive or S3, or have every import land in your own bucket.

Metadata only

For a title, duration and thumbnail without downloading anything, use POST https://api.importly.io/metadata/basic with { "url": "..." } and the same polling loop against /metadata/basic/status. See Metadata.

When a node fails

The HTTP Request node marks the run as failed on a 4xx or 5xx response. The JSON body says why, with a code such as INSUFFICIENT_BALANCE or INVALID_URL. Turn on the node’s Continue On Fail setting (or On Error: Continue) if you want to branch on the error instead of stopping. Every code is listed in Errors. Using Make or Zapier instead? See Make or Zapier.