Delete Cloud

Removes a file from a connected cloud storage location.

Delete Cloud deletes a single file from cloud storage.

Use a Delete Cloud node in your Flow to clean up after processing, removing an import file once its contents have been stored, clearing a temporary export after it has been collected, or removing files that are no longer needed.

Delete Cloud does not open a source stream and does not require Sink Collect. It works in an ordinary row.

To configure a Delete Cloud node in the Flow Editor, drag it from the Stream group in the Palette to the Workspace canvas, then double-click the node to open and configure its behavior.

General tab

• Name — optional display name for the node in the editor. By default the node shows a label of "Delete Cloud"; the value you provide here replaces it.

• Config — the tenant configuration. Defaults to the current tenant.

• Connection — the storage connection to delete from. Selected from the connections configured for the tenant. Required.

• Remote Path — the path of the file to delete. Required.

Delete Cloud has no Output field, unlike Read Cloud and List Cloud.

Remote paths

For AWS S3 and Azure Blob connections without a configured bucket or container, use the following format for Remote Path. When the connection already specifies the bucket or container, use only the object path. SFTP paths are passed through verbatim.

<container>/<path/to/file>

Deleting data.txt from a container named test therefore uses test/data.txt.

For AWS S3 and Azure Blob, List Cloud returns object paths relative to the bucket or container. Prepend the bucket or container only when the Delete Cloud connection does not already specify it. For SFTP, combine the listed file name with its remote directory path.

Deleting a file

On success, Delete Cloud forwards the incoming message and adds no deletion result. When processing a source, it forwards each source item after its deletion completes.

Missing-file behavior depends on connection type. Azure Blob ignores an absent blob. SFTP reports an error and sends no normal downstream message, so do not rely on missing-file deletion being idempotent across connection types.

Missing-file behavior and error details from Read Cloud depend on the connection provider.

Deletion takes effect immediately. A Read Cloud node run against the same path afterwards fails with the error above.

Source tab

The Source tab controls how the node behaves when it is processing a source stream rather than a single message.

• Parallelism can be set to None, Ordered, or Unordered

• Max — the concurrency ceiling used by Ordered and Unordered

The tab itself notes: Configurations in this tab are only active when this node is in a source. Outside a source stream the node processes a single message, and Parallelism and Max have no effect.

Example

A Flow removes a temporary file from storage.

[GET] /delete → Delete Cloud → HTTP Response

Configure the Delete Cloud node

Set Connection to the storage connection and Remote Path to the file to remove. For example, use test/data.txt when the connection has no configured bucket or container, or data.txt when it already specifies test. For SFTP, use the remote server path.

Run the deletion

Add an HTTP Response node and request /delete. Delete Cloud forwards the incoming message without adding a deletion result.

Confirm the file is gone

Run a List Cloud node against the container. The deleted path no longer appears. Missing-file behavior and error details from a Read Cloud node depend on the connection provider.