MK.IO — Media Services & Transcoding
Connect MK.IO to Enveu Flow and automate media processing, asset management, and publishing as part of your media operations pipeline.
What this integration does
Connect MK.IO to Enveu Flow and automate media processing, asset management, and publishing as part of your media operations pipeline.
Best for
Connecting MK.IO transcoding and packaging into automated ingest, processing, and delivery workflows for OTT platforms.
Manage media assets, trigger encoding jobs, and automate publishing workflows with MK.IO. Use in Live to VoD and Content Migration workflows for cloud-native media processing.
Inputs & outputs.
Inputs
Source asset URL
File to submit for transcoding or packaging
Transform preset
Transcoding profile or packaging configuration
Output storage
Destination storage for transcoded outputs
Outputs
Output asset URLs
URLs of transcoded renditions in configured formats
Job status
Transcoding job completion status and error details
Triggers & actions.
Triggers
Job completed
Fires when a transcoding or packaging job finishes in MK.IO
Job failed
Fires when a processing job errors — triggers error handling or retry workflow
Actions
Create job
Submit a transcoding or packaging job with a configured preset
Get job status
Poll the status of an in-progress transcoding job
List assets
Enumerate media assets in your MK.IO environment
Delete asset
Remove a processed asset from MK.IO storage
Example workflow.
Source asset uploaded
Storage trigger
→
Submit transcode job
MK.IO action
→
Poll job status
MK.IO action
→
Upload output
Amazon S3
→
Notify
Slack
Used in these workflows.
Frequently asked questions.
Flow connects to MK.IO using your Subscription Name, API Token, and Storage Account Name, stored securely in the Flow vault.
Yes. Flow can submit encoding and packaging jobs to MK.IO as a workflow action. The job configuration - transform, output format, and storage destination - is defined in your workflow settings.
Yes. Flow can create streaming locators for MK.IO assets and return the playback URL for use in downstream steps such as CMS publishing or notification.
Yes. The MK.IO plugin supports asset created and job completed triggers, allowing workflows to fire automatically when new content arrives or processing finishes.