Integrations

Importing from Adilo

Move supported videos and details from Adilo into a Playflow Fleet workspace.

Availability and access

Adilo import is available only on Fleet. A workspace owner or admin can connect it in workspace settings. Other plans cannot start an import.

Enter that workspace's Adilo public and secret API keys. Playflow encrypts the keys for that workspace. Connecting validates them with a read-only request. After saving, Playflow shows masked values rather than the keys. An owner or admin can reconnect with new keys or disconnect the integration. An active import must finish before either change.

Choose and preview

Select a source project. Choose an existing destination folder or enter a new folder name. Run the dry run before starting. It lists eligible and skipped videos, estimated bytes, and the best available rendition for each item.

The best available rendition may be 720p when Adilo does not provide 1080p. The preview is an estimate and does not reserve storage.

Start API request

To start through POST /api/integrations/adilo/imports, send projectId and optionally folderId, newFolderName, mirrorFolders, and fileIds. fileIds is an optional non-empty array of unique Adilo file IDs. Leave it absent to import all currently eligible files in the project. Include it to import only the selected eligible files.

Playflow revalidates the project with a fresh preview when starting. If any selected ID is unknown or no longer eligible, the whole request returns 400 and no import is queued.

What transfers

Playflow transfers video files with their titles, descriptions, and tags, plus available captions. Each Adilo subtitle or translation becomes the transcript for its language in Playflow. When Adilo exposes reliable folder membership for the selected project, you can mirror its folder names and parent relationships under the chosen Playflow destination. If membership is unavailable, the videos import flat into that destination. The Adilo account we verified did not expose folder membership, so its preview is flat.

If Adilo returns 404 for a video detail or metadata request, that item is recorded as unavailable and the import continues. A 404 for one subtitle language skips only that language, so another available language can still import. Playflow does not treat the missing caption data as a video import failure, and it never removes a caption track that already exists.

Bring over captions for earlier imports

Use Bring over captions for videos imported before caption transfer was enabled. The backfill checks each imported video separately, records an audit entry, and does not import the media again. Missing Adilo data is skipped as unavailable, existing Playflow captions are preserved, and the backfill continues with the remaining videos. See the dedicated Adilo caption backfill guide for selection, paging, limits, and result details.

Backfill API request

Call POST /api/integrations/adilo/captions/backfill. Send either videoIds, an array of 1 to 4 unique Playflow video UUIDs, or cursor, a Playflow video UUID returned as nextCursor. The fields are mutually exclusive. Send {} to start an automatic backfill from the beginning, then continue with each returned cursor until nextCursor is null.

{"videoIds":["3bc834ee-1f65-4a0f-928b-b533cc8a1843"]}

A 200 response contains {"backfill": ...}. The backfill object has total, imported, unavailable, failed, nextCursor, and items. Each item has videoId, title, a status of imported, unavailable, or failed, plus languages, errors, and nullable reason.

Views, calls to action, contacts, DRM-protected videos, and non-video files do not transfer.

Quotas and duplicates

Imports use the workspace's existing storage, video-count, and per-file limits. Items outside those limits are skipped or fail with a reason. Already imported source videos are skipped so that rerunning a selection does not intentionally create duplicates.

Start, monitor, and retry

After reviewing the dry run, start the import and follow queued, running, completed, skipped, and failed counts in the progress view. A workspace can run one import at a time. Individual items keep their status and reason, so an import can complete with partial failures.

Retry runs only failed items that are safe to attempt again. If Playflow cannot determine whether the external transfer created a video, that item is marked ambiguous and is not retried automatically. Review ambiguous items before taking further action to avoid a duplicate.