Skip to content
Start in the sandboxStart free
All connectors
HeyGen logo

HeyGen

Content creation & media

Move briefs, assets and sign-offs through HeyGen without chasing between tools.

13 ways to read, 2 ways to write, each write switched on by you.

Try this in the sandboxBring us a workflow

Quality checks

Built and tested with example responses.

  1. Ready to connect: doneEvery listed action is built in.
  2. Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
HeyGen with Nexra

Connected, approved, proven.

The things teams do most with HeyGen, an example flow with a person in the loop, and what Nexra keeps as proof.

Top actions

  • Generate video from templateApproval by rule
  • Generate avatar videoApproval by rule
  • List avatar looksRead

Example flow

  1. HeyGen · List avatar looksDone
  2. HeyGen · Generate video from templateNeeds approval
  3. Nexra · Record the decision and result in the evidence chainProven

Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches HeyGen.

What gets logged

  • Whether it ran on its own or who approved it, and under which rule
  • A fingerprint of the exact request sent to HeyGen
  • HeyGen's reply: what it created or changed
  • One entry in the evidence chain, linked to the one before

Try this in the sandbox

Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.

Try this in the sandboxBring us a workflow

For developers

Technical detail

Read HeyGen avatars, looks, voices, templates, videos and credits, and generate avatar videos from scripts or templates (billable, idempotency-keyed, never retried).

HeyGen API docs
Source actions
13
Destination actions
2
Data types
10

What you can map

Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.

Avatar looks2
  • Get avatar lookSource

    Get an avatar look's supported engines, orientation and preview.

  • List avatar looksSource

    List avatar looks (outfits and styles). A look ID is the avatar ID for Generate avatar video.

Avatars2
  • Get avatar groupSource

    Get an avatar group's name, looks count, default voice and training status.

  • List avatar groupsSource

    List avatar groups (characters), public or your own private avatars.

Template videos1
  • Generate video from templateDestinationNot retried automaticallyApproval before production

    Render a video from a HeyGen Studio template by replacing its variables. Billable: consumes API credits. Sharing stays off.

Templates2
  • Get templateSource

    Get a template's variables (with current defaults) and scene IDs.

  • List templatesSource

    List API-ready HeyGen Studio templates in the workspace.

User1
  • Get account and creditsSource

    Get the API plan, wallet balance and credit usage for the API key's account.

Video statuses1
  • Get video statusesSource

    Get the status of up to 100 videos in one call.

Videos3
  • Generate avatar videoDestinationNot retried automaticallyApproval before production

    Render a video of an existing avatar look speaking a script. Billable: consumes API credits. Poll Get video for status.

  • Get videoSource

    Get a video's status, duration, presigned download URLs and failure details. Poll this after generating.

  • List videosSource

    List videos in the account, optionally in one folder or matching a title.

Voices1
  • List voicesSource

    List public or private voices, filtered by engine, language and gender.

Webhook endpoints1
  • List webhook endpointsSource

    List registered webhook endpoints and the events they receive.

Webhook event types1
  • List webhook event typesSource

    List the webhook event types HeyGen can deliver.

Access and limits

Authentication
HeyGen API key (x-api-key header)
Plans and access
HeyGen API plans (pay-as-you-go or Enterprise) with an API key. API usage bills API credits, separate from app subscription credits. API keys can be scoped; a key without the needed scope returns insufficient_api_key_scope. Concurrent renders are capped by plan (10 on pay-as-you-go, 20 on Enterprise). Some accounts must complete SMS verification before generating.
Test environment
HeyGen has no sandbox. Every successful generation consumes API credits; test with short scripts.
Rate limits
HeyGen returns HTTP 429 with rate_limit_exceeded and a Retry-After header; Nexra honours it on reads. Concurrent renders are limited by plan. Generation is billable and never retried automatically.
Pagination
List endpoints use limit and an opaque token (next_token while has_more). Maximum page sizes: avatars and looks 50; videos, voices, templates and webhook endpoints 100.
Provider events
HeyGen webhook endpoints for avatar_video.success, avatar_video.fail and other events, signed with a per-endpoint secret. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.

Before you build a flow

  • Generate avatar video and Generate video from template are billable: they consume API credits. They are never retried automatically. HeyGen's Idempotency-Key header is sent with the Nexra execution key, so a manual repeat of the same step is deduplicated by HeyGen; a different execution renders again.
  • Avatar videos only use existing avatar looks (avatar_id from List avatar looks). Animating an arbitrary image (type image), cinematic avatars, studio compositions, Video Agent, translation, lipsync and AI clipping are not exposed.
  • The rendered MP4 is not downloaded: Get video returns presigned video, caption and subtitle URLs. Binary upload and download (assets, audio) is an engine gap, so scripts are text-to-speech only (no audio_url or audio asset).
  • Template videos are generated with enable_sharing fixed to false, so no public share page is created. callback_url is not exposed; use registered webhook endpoints instead.
  • Excluded by design: avatar, look, voice and template creation or editing, avatar consent, voice cloning and design, folder creation, webhook endpoint changes, and every delete.
  • Get user omits the username, email and names; it returns plan, wallet balance and credit usage only.
  • Insufficient credit (insufficient_credit), exhausted quotas (quota_exceeded) and HTTP 402 are classified as permission errors so they are not retried.
  • No updated-since filter is documented for videos; filter by folder or title.

Developer reference

  1. Create the HeyGen credentials described above with the narrowest permissions your flows need.
  2. In Nexra, open Connect, then Connections, then New connection, choose HeyGen, enter its settings and credentials, and tick only the write actions you need. Connection guide
  3. Test the connection, then use its actions as flow sources and destinations. Flow guide
HeyGen docsAPI referenceHeyGen docsAuthenticationHeyGen docsRate limitsHeyGen docsWebhooks

Machine-readable detail: GET /api/public/connect/connectors/heygen and the Connections API.