Azure Blob Storage: Upload a file

🕙  2 minute read

Use this action to upload a blob to an Azure blob storage container.

How to configure this action

This action requires a preconfigured Azure Blob Storage integration. For more information on integrating Catalytic with other systems, please refer to the Integrations section of our help center, or the Azure Blob Storage Integration Setup Guide directly.

The file size must be within Catalytic’s file size limit.

Fields for this action

  • Integration

    • Select your Azure Blob Storage integration from the options. You may have multiple integrations configured.
  • Container name

    • Enter of the name of the container to upload the blob to. Tools like Azure Storage Explorer can help to navigate your Azure storage.
    • Set Create new container to true to create a new container if the container name does not exist.
  • Create new container

    • You can configure this action to create a new container if the Container name above does not exist.
    • Select True to create a new container if the container name above does not exist.
    • Select False to never create a new container.
  • Blob Name

    • Enter the name and type of the blob you are uploading, for example filename.pdf.
    • If no name is provided, the file name will be used by default.
  • Container public access level

    • If Create new container is True, set the container public access level if a new container is created because the specified container does not exist. Containers are set to Private by default.
      • Choose Private to block all public access.
      • Choose Container to make the new container and all blobs it contains publicly accessible.
      • Choose Blob to make all blobs in the container public but leave the container itself private.
  • Metadata

    • To include metadata with the uploaded file, provide each as a key/value pair, separated by a new line, for example:

      - Company:Vandelay
      - Title:Industrialist
      
    • Azure blob storage metadata is used to store additional values with the resource. Note that Metadata values don’t affect how the blob behaves.

  • File to upload

    • Specify the file to upload, Use a field reference to a file uploaded in a prior task or instance. Instance fields are a useful place to store and collect files for your Workflow.
  • Output field name

    • Enter the name for the field in which the result should be saved.

What will this output?

This action will output a field with the downloaded blob. The field will depend on the Output field name set during configuration.

Output fields for this action

  • Blob name

    • The blob name. This will be the Blob Name set during configuration, or the name of the file if the blob was unset.
  • Container

    • The path of the container where the blob was uploaded
  • Container created

    • True or False for whether a new container was created.
  • eTag

    • The eTag associated with the upload. This is a identifier used by Azure to keep track of updates, when they were made, and who made them.

Sorry about that. What was the most unhelpful part?









Thanks for your feedback

We update the Help Center daily, so expect changes soon.

Link Copied

Paste this URL anywhere to link straight to the section.

Need more help?

If you're signed in to Catalytic Community, you can ask other users a question. You'll be redirected to Community where you can add more info.