Nexra
All connectors
Implemented
Content creation & media
Frame.io logo

Frame.io

Frame.io V4 accounts, workspaces, projects, folders, files, version stacks, metadata, comments and review links, plus comments and remote (URL) uploads.

Bring review status, comments and assets from Frame.io into production trackers and project tools, post feedback from other systems and pull finished files in from storage.

Build a flow with Frame.ioProvider API documentation

Source actions

22

Destination actions

2

Data types

16

Validation status

Implemented · fixture tested.

Implementation is checked against provider-shaped fixtures for every action, authentication failures, rate limits, pagination and duplicate safety. Provider sandbox and authorised account validation are recorded separately when credential-backed runs are completed.

What you can map

accounts
  • List accounts
    Source

    Frame.io accounts the authorised user belongs to, with roles and storage.

    accounts.list
assets
  • Search the account
    Source

    Searches files, folders, version stacks and projects by name and content.

    assets.search
comments
  • Comment on a file
    Destination
    Not retried automatically
    Approval before production

    Adds a comment to a file, optionally at a frame (video) or page (PDF).

    comments.create
  • Get comment
    Source

    One comment, optionally with replies.

    comments.get
  • List file comments
    Source

    Comments on a file, optionally with replies and owner display names.

    comments.list
file metadata
  • Get file metadata
    Source

    Metadata field values (system and custom fields) for one file.

    file_metadata.get
file upload status
  • Get file upload status
    Source

    Whether a file's upload (including a remote upload) has completed or failed.

    file_upload_status.get
files
  • Get file
    Source

    One file with status, size, media type and (optionally) metadata.

    files.get
  • List files in a folder
    Source

    Files directly inside a folder, with status, size and media type.

    files.list
folder children
  • List folder contents
    Source

    Files, folders and version stacks directly inside a folder.

    folder_children.list
folders
  • Get folder
    Source

    One folder.

    folders.get
  • List subfolders
    Source

    Folders directly inside a folder (use a project's rootFolderId to start).

    folders.list
metadata fields
  • List metadata field definitions
    Source

    Account-level metadata (custom) field definitions.

    metadata_fields.list
projects
  • Get project
    Source

    One project, including its root folder ID.

    projects.get
  • List projects
    Source

    Projects in one workspace, or every project in the account when no workspace is given.

    projects.list
remote uploads
  • Upload file from URL
    Destination
    Not retried automatically
    Approval before production

    Creates a file in a folder that Frame.io fetches from an HTTPS URL (remote upload).

    remote_uploads.create
share assets
  • List review link assets
    Source

    Assets included in a share (review link).

    share_assets.list
shares
  • Get review link
    Source

    One share (review link). Read only.

    shares.get
  • List review links
    Source

    Shares (review links) on a project, with access, expiry and permissions. Read only.

    shares.list
version stack versions
  • List versions in a stack
    Source

    The files (versions) inside a version stack.

    version_stack_versions.list
version stacks
  • Get version stack
    Source

    One version stack with its head version.

    version_stacks.get
  • List version stacks in a folder
    Source

    Version stacks directly inside a folder, with the head version.

    version_stacks.list
workspaces
  • Get workspace
    Source

    One workspace.

    workspaces.get
  • List workspaces
    Source

    Workspaces in the account.

    workspaces.list

Authentication

Adobe IMS OAuth client and refresh token

Plans and access

Frame.io V4 accounts administered through the Adobe Admin Console, or Frame-managed accounts switched to Adobe authentication. Requires an OAuth Web App credential for the Frame.io API in the Adobe Developer Console. Results are limited to what the authorising user can see.

Test environment

Frame.io has no sandbox. Use a test workspace or project; remote uploads consume account storage.

Rate limits

Frame.io uses leaky-bucket limits per account user and endpoint, documented in the OpenAPI file: most reads and comments 100 calls per minute; file, folder and version-stack listings and remote uploads 5 calls per second; file details 10 per second. HTTP 429 is retried with backoff (Retry-After when present).

Pagination

Cursor pagination: page_size up to 100 (default 50); links.next carries an opaque after cursor. Single-direction only.

Provider events

Frame.io V4 supports workspace webhooks (file, comment, review and share events). Nexra event triggers are not yet available; flows run on demand or on a schedule.

Before you build a flow

  • Never deletes files, folders, version stacks, projects, workspaces, comments, shares or webhooks, and never moves, copies or renames assets.
  • Review links (shares) are read only: creating shares, changing their access or adding reviewers is not offered, so Nexra never opens assets to public viewing. Share passphrases are never mapped.
  • Local (binary) uploads, media-link downloads and comment attachments are not offered. Remote uploads ask Frame.io to fetch a file from an HTTPS URL; poll file_upload_status.get afterwards.
  • User e-mail addresses (creators, comment authors, reviewers) are never mapped; only user IDs and display names. Share reviewers and user-role lists are not offered.
  • There is no updatedSince filter. Sort listings by updated_at descending where the endpoint allows.
  • Legacy developer tokens (x-frameio-legacy-token-auth) and server-to-server credentials are not supported; use an OAuth Web App credential.
  • Workspace, project, folder and metadata-field writes, custom actions and webhook management are not offered.

Developer reference

  1. Create the Adobe credentials described above with the narrowest permissions your flows need.
  2. In Nexra, open Connect, then Connections, then New connection, choose Frame.io, 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
Adobe docsAPI referenceAdobe docsAuthenticationAdobe docsRate limitsAdobe docsWebhooks

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