{"id":22541,"date":"2021-11-02T15:21:37","date_gmt":"2021-11-02T15:21:37","guid":{"rendered":"http:\/\/build_workflows_with_cloudinary_s_mediaflows"},"modified":"2025-03-02T09:44:24","modified_gmt":"2025-03-02T17:44:24","slug":"build_workflows_with_cloudinary_s_mediaflows","status":"publish","type":"post","link":"https:\/\/cloudinary.com\/blog\/build_workflows_with_cloudinary_s_mediaflows","title":{"rendered":"Build Workflows With Cloudinary\u2019s MediaFlows"},"content":{"rendered":"

Many of you who work with the Cloudinary platform have a media-associated workflow for moderation of images, dispatch of notifications with certain data or headers, implementation of activities through add-ons, etc. For most of those cases, Cloudinary would suggest that you take advantage of our webhook notifications<\/a> and build the workflow with an infrastructure like AWS Lambda. This post describes how to do that with Cloudinary\u2019s MediaFlows<\/a> a beta<\/strong> product that helps tackle management and operational tasks related to visual media.<\/p>\n

\"Waterfall\"<\/p>\n

What exactly is MediaFlows, you wonder? Here\u2019s the official description:<\/p>\n

MediaFlows connects Cloudinary\u2019s APIs and services with a visual interface. Developers and marketers can design, deploy, and automate custom media applications and processes in minutes, not days.<\/em><\/p>\n

Based on drag-and-drop, MediaFlows automates the process of receiving notifications and acting on the changes to your media resources on Cloudinary. The simple use case below typifies a MediaFlows process:<\/p>\n

    \n
  1. You upload images to Cloudinary.<\/li>\n
  2. You move the images to a designated folder with a preset, which also enables manual moderation.<\/li>\n
  3. The moderators review the images and approve or reject the media.<\/li>\n
  4. Cloudinary automatically moves the approved images to a folder called Approved.<\/li>\n<\/ol>\n
    Note:<\/strong>

    For an in-depth discussion of moderation with Cloudinary, see Nadav Soferman\u2019s article<\/a>.<\/p><\/div>\n

    Below is a tutorial that shows you how to create workflows with Cloudinary\u2019s MediaFlows.<\/p>\n

    Step 1: Upload Images to Cloudinary<\/h2>\n

    \"Step<\/p>\n

    First, ensure that uploaded images to Cloudinary land in a certain folder, marked for moderation. Do the following:<\/p>\n

      \n
    1. Create an upload preset<\/a> in which to specify a folder called toBeModerated<\/code> as the target.<\/li>\n
    2. Set up this parameter: Auto Moderation: manual<\/code>.<\/li>\n
    3. Name the preset moderate<\/code>.<\/li>\n<\/ol>\n

      \"Example<\/p>\n

      You can browse the settings of the preset with the Admin API<\/a>.<\/p>\n

      $ cld admin upload_preset moderate\n\n{\n "name": "moderate",\n "unsigned": false,\n "settings": {\n   "overwrite": true,\n   "use_filename": true,\n   "unique_filename": false,\n   "type": "upload",\n   "moderation": "manual",\n   "folder": "toBeModerated"\n }\n}\n<\/code><\/pre>\n
      Step 2: Create the MediaFlow<\/h2>\n
      Now create a MediaFlows account and link it to your Cloudinary account, as follows.<\/p>\n
      Sign Up With MediaFlows<\/h3>\n
        \n
      1. Go to mediaflows.cloudinary.com\/<\/code><\/a>, click the Sign In<\/strong> button, and create a new account with Gmail or GitHub. (For now, those are the only ways for setting up MediaFlows accounts.)<\/li>\n
      2. Create a project called Moderation<\/strong>.<\/li>\n
      3. Click Connect with Cloudinary<\/strong> to map the MediaFlow account to one on Cloudinary. When prompted, log in to Cloudinary.<\/li>\n<\/ol>\n
        Note:<\/strong> 
        If you have multiple subaccounts with Cloudinary, you will be asked to pick one. Because MediaFlows operates at the subaccount level, you cannot enable the same task for multiple subaccounts.<\/p><\/div>\n
        \"Setting<\/p>\n
        Build Your Workflow<\/h3>\n
        You can now use MediaFlows to build a workflow. Follow these two steps:<\/p>\n
        \"Setting<\/p>\n
        Set Up Notifications<\/h4>\n
        At the outset, create a basic flow by clicking Start from basic<\/strong>.<\/p>\n
        \"Create<\/p>\n
        A dialog box titled Catch Webhook<\/strong> is displayed, denoting that you will be notified of changes in your Cloudinary account. For details, double-click the dialog box. Note down the URL for a later step.<\/p>\n
        \"Catch<\/p>\n
        Check for Approval and Move the Image<\/h4>\n
        This step is the core of the MediaFlows setup: You\u2019ll verify if the notification is for an image that has been approved and, if so, have MediaFlows move the image to a folder you specify.<\/p>\n
        The notification on an approval reads like this:<\/p>\n
        {\n  \"asset_id\"<\/span>: \"9f377ced45037da942fbd1883c27b98d\"<\/span>,\n  \"moderation_status\"<\/span>: \"approved\"<\/span>,\n  \"url\"<\/span>: \"http:\/\/res.cloudinary.com\/dbmataac4\/image\/upload\/v1633466870\/toBeModerated\/aaa4.jpg\"<\/span>,\n  \"version\"<\/span>: 1633466870<\/span>,\n  \"moderation_updated_at\"<\/span>: \"2021-10-05T20:47:55Z\"<\/span>,\n  \"etag\"<\/span>: \"982dc96b643b044c55a1d8be8c2d0e29\"<\/span>,\n  \"moderation_kind\"<\/span>: \"manual\"<\/span>,\n  \"secure_url\"<\/span>: \"https:\/\/res.cloudinary.com\/dbmataac4\/image\/upload\/v1633466870\/toBeModerated\/aaa4.jpg\"<\/span>,\n  \"public_id\"<\/span>: \"toBeModerated\/aaa4\"<\/span>,\n  \"notification_type\"<\/span>: \"moderation\"<\/span>,\n  \"uploaded_at\"<\/span>: \"2021-10-05T20:47:50Z\"<\/span>\n}\n<\/code><\/span>Code language:<\/span> JSON \/ JSON with Comments<\/span> (<\/span>json<\/span>)<\/span><\/small><\/pre>\n
        The important fields for approval are\u2014<\/p>\n