[Yandex Cloud documentation](../../../../index.md) > [Yandex Serverless Integrations](../../../index.md) > [Step-by-step guides](../../index.md) > Workflows > [Workflow step constructor](index.md) > Integration steps > Serverless Containers

# Invoking a Yandex Serverless Containers container

{% list tabs %}

- Management console {#console}

  1. When [creating](../workflow/create-constructor.md) a new workflow or [editing](../workflow/update.md) an existing one, in the management console, under **Create workflow** / **Edit workflow**, select `Constructor`. 
  1. From the **Integration steps** section on the left side of the screen, drag the ![serverless-container-icon](../../../../_assets/serverless-container-icon.svg) **Serverless Containers** element to the relevant workflow location in the constructor window.

      You can drag and drop steps into areas marked by the dotted line in the workflow schema, such as **Add a step**, etc.
  1. In the workflow schema window, click the new **Serverless Containers** section to select it.
  1. At the right of the window, on the **Settings** tab.

      1. In the **Step name** field, enter a name for the workflow step.
      1. In the **Container** field, select the container to invoke during this step.
      1. In the **Request method** field, select the HTTP request method.
      1. Optionally, specify the HTTP request path in the **Request path** field.
      1. Optionally, in the **Request query parameters** field, click ![plus](../../../../_assets/console-icons/plus.svg) **Add parameter** to add a query parameter in `<Parameter_name>`:`<Parameter_value>` format to the HTTP request.

          To add multiple query parameters, click ![plus](../../../../_assets/console-icons/plus.svg) **Add parameter** as many times as needed.

          To remove the query parameter you do not need, click ![trash-bin](../../../../_assets/console-icons/trash-bin.svg) in the same row.
      1. Optionally, in the **Request headers** field, click ![plus](../../../../_assets/console-icons/plus.svg) **Add header** to add a header in `<Header_name>`:`<Header_value>` format to the HTTP request.

          To add multiple headers, click ![plus](../../../../_assets/console-icons/plus.svg) **Add header** as many times as needed.

          To remove the header you do not need, click ![trash-bin](../../../../_assets/console-icons/trash-bin.svg) in the same row.
      1. Optionally, specify the HTTP request body in the **Request body** field.
      1. Optionally, in the **Timeout, ms** field, set the maximum execution time for the current step.
      1. Optionally, to set a custom retry policy for a step, expand the **Retry policy** section and click ![plus](../../../../_assets/console-icons/plus.svg) **Retry policy**. In the form that appears:
         
         1. Optionally, in the **Initial delay, ms** field, set the initial value for a delay between step retries.
         1. Optionally, in the **Backoff rate** field, set the multiplication factor for delay before each step retry.
         1. Optionally, in the **Maximum delay, ms** field, set the value for a maximum delay between step retries.
         1. In the **Errors** field, select the errors for which the step will or will not be retried.
         
             For detailed information about possible errors, see [this section](../../../concepts/workflows/execution.md#errors).
         1. Optionally, in the **Maximum number of retries** field, set the maximum number of step retry attempts.
         1. In the **Error selection mode** field, select:
         
             * `INCLUDE`: Retry executing a step when errors specified in the **Errors** field occur.
             * `EXCLUDE`: To retry executing the step on any errors other than those specified in the **Errors** field.
         
         If you want to delete a retry policy you created for the step earlier, click ![ellipsis](../../../../_assets/console-icons/ellipsis.svg) and select **Delete** in the **Retry policy** row.
         
         If no custom retry policy is configured for a step, the retry policy [set for the whole workflow](setup-restart-policy.md) will apply.
  1. Optionally, navigate to the **Input** tab and set a [jq template](../../../concepts/workflows/templating.md) to filter the [workflow state](../../../concepts/workflows/workflow.md#state) fed into the step.
  1. Optionally, navigate to the **Output** tab and set a [jq template](../../../concepts/workflows/templating.md) to filter the step outputs added into the [workflow state](../../../concepts/workflows/workflow.md#state).
  1. Optionally, [add](setup-catch-rule.md) an [error transition rule](../../../concepts/workflows/yawl/index.md#catchrule) for the step you are creating to handle errors you may get during this step.

{% endlist %}

## Useful links {#see-also}

* [YaWL specification](../../../concepts/workflows/yawl/integration/containercall.md)
* [Creating a workflow using the constructor](../workflow/create-constructor.md)
* [Updating a workflow](../workflow/update.md)