# Assign a Managed Input to a Workflow

Having only managed inputs all by themselves is good but they are created for a purpose, which is to have them assigned to a workflow. Below we will look at the steps required to have a Managed Input assigned to a workflow.

First of all we need to have the Managed Input ID at hand, this can be obtained via the following endpoint:

GET ​/managed-inputs

This endpoint returns an array of items which contains all of the created inputs the response looks like this:

{
  "items": [
    {
      "id": "720ac39d-f165-479a-8bba-903eb894a51b",
      "name": "RTMP Push Input",
      "region": "eu-west-1",
      "type": "VIRTUAL_INPUT",
      "protocol": "RTMP_PUSH",
      "status": "DETACHED",
      "sources": [],
      "allowedCidrBlocks": [
        "0.0.0.0/0"
      ]
    },
    {
      "id": "8a1e9a0f-c0e6-4459-8736-dea254ba7ca5",
      "name": "ManagedInput1",
      "region": "eu-west-1",
      "type": "VIRTUAL_INPUT",
      "protocol": "RTMP_PUSH",
      "status": "DETACHED"
    }
  ]
}

The endpoint also accepts an optional parameter which is called region. Using this endpoint allows us to list Managed Inputs only in a particular region. This is useful when there are more than one regions being used and we want to see the managed inputs created in one particular region.

Since this is a GET request the region parameter is passed on like this:

GET /managed-inputs?region=eu-west-1

For information on how to get all of the supported regions for the Live Service you can check the following page: Insert Link to Regions Page

Now that we have our Managed Inputs listed we can get the ID of the input we would like to use for a workflow.