Brightcove — Cloud Video Platform Integration
Connect Brightcove to Enveu Flow and automate video ingest, metadata updates, and publishing as part of your media operations pipeline.
What this integration does
Connect Brightcove to Enveu Flow and automate video ingest, metadata updates, and publishing as part of your media operations pipeline.
Best for
Ingesting processed assets, updating metadata, and publishing content to Brightcove as the final step of any automated media workflow.
Trigger workflows from Brightcove video events, ingest recordings, update metadata, and publish assets back to Brightcove. Use in Live to VoD, Content Migration, and Multilingual Metadata workflows.
Inputs & outputs.
Inputs
Video file URL
Processed asset URL to ingest into Brightcove
Metadata object
Title, description, tags, and custom fields for the video
Account ID
Brightcove account to publish into
Outputs
Brightcove video ID
Unique ID of the created or updated video asset
Playback URL
Brightcove delivery URL for the published asset
Triggers & actions.
Triggers
Video ingested
Fires when a new asset lands in your Brightcove account
Status changed
Asset moves to active, inactive, or pending publish
Live stream ends
Recording is available and ready for processing
Actions
Get video
Fetch asset details, playback URLs, and metadata
Update metadata
Title, description, tags, custom fields, and scheduling
Ingest video
Upload and transcode via Dynamic Delivery
Add text track
Attach SRT or VTT subtitle files to an asset
Delete video
Remove an asset from your Brightcove catalog
Example workflow.
Live stream ends
Brightcove trigger
→
Transcode
Mux
→
Generate subtitles
Gladia
→
Update metadata
Brightcove action
→
VoD live
Published
Used in these workflows.
Frequently asked questions.
Flow connects to Brightcove using OAuth 2.0 client credentials - Client ID and Client Secret - stored securely in the Flow vault. You configure the Account ID and credentials once per workspace.
Yes. The Brightcove plugin supports a video-ingested trigger that fires automatically when a new asset lands in your Brightcove account. No polling required - the trigger uses Brightcove notifications.
Yes. Flow can update any Brightcove metadata field - title, description, tags, custom fields, scheduling dates, and geo-restrictions - as a workflow action. Metadata updates can be triggered by upstream steps such as translation or AI enrichment.
Yes. The Brightcove ingest action uses Dynamic Delivery by default. You configure your ingest profile in the workflow and Flow submits the ingest job to Brightcove automatically.