Interacting with Yandex Object Storage objects

When creating a new workflow or editing an existing one, in the management console, under Create workflow / Edit workflow, select Constructor.

From the Integration steps section on the left side of the screen, drag the Object Storage 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.

In the workflow schema window, click the new Object Storage section to select it.

At the right of the window, on the Settings tab.

1. In the Step name field, enter a name for the workflow step.

2. In the Bucket field, select the bucket containing the objects you will work with as part of your workflow.

3. In the Object name field, specify the name of the object you are going to work with.

4. In the Action field, select:

   • Add object to add a new object to the bucket.
   • Get object to get object content from the bucket.

5. In the Content type field, select the content type of the target object:

   If you are adding an object to the bucket

   • BINARY: Object content will be decoded from Base64 format.
   • TEXT: Object content will be saved as UTF-8 encoded plain text. If the file has a different encoding, Workflows will return an error, or the workflow will run incorrectly.
   • JSON: Object text containing JSON will be saved as a JSON structure.
   If you are getting an object from the bucket

   • BINARY: Object content will be encoded in Base64 format.
   • JSON: Object content will be received as a JSON structure.
   • TEXT: Object content will be received as UTF-8 encoded plain text. If the file has a different encoding, Workflows will return an error, or the workflow will run incorrectly.
   • EXCEL: Object content will be converted into an array of pages, where each page is an array of string arrays. Supported formats: XLAM, XLSM, XLSX, XLTM, and XLTX.
   • CSV: Object content will be converted into an array of string arrays by dividing the strings based on the following separators: comma (,) and line break.

6. If you are adding an object to the bucket, specify the content of the new object in the Object content field.

7. Optionally, in the Timeout, ms field, set the maximum execution time for the current step.

8. Optionally, to set a custom retry policy for a step, expand the Retry policy section and click 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.

   2. Optionally, in the Backoff rate field, set the multiplication factor for delay before each step retry.

   3. Optionally, in the Maximum delay, ms field, set the value for a maximum delay between step retries.

   4. 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.

   5. Optionally, in the Maximum number of retries field, set the maximum number of step retry attempts.

   6. 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 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 will apply.

Optionally, navigate to the Input tab and set a jq template to filter the workflow state fed into the step.

Optionally, navigate to the Output tab and set a jq template to filter the step outputs added into the workflow state.

Optionally, add an error transition rule for the step you are creating to handle errors you may get during this step.