# Cloud Integration for Files ### Cloud Integration for Files When you configure a [File Job](https://docs.tricloudnexus.io/management-portal/designer/assets/jobs/file-job), [FTP Job](https://docs.tricloudnexus.io/management-portal/designer/assets/jobs/ftp-job), or [File Share Job](https://docs.tricloudnexus.io/management-portal/designer/assets/jobs/file-share-job) in Tricloud Nexus and choose the option **Send files to Cloud**, the selected files are automatically uploaded to your environments **Ingestion Storage Account**. This makes it simple to centralize, archive, or further process files collected at the Edge -without any manual file transfers or additional integration work. *** ### Cloud Storage Location All files sent to the cloud are placed in the **files-drop** container of your configured ingestion storage account. By default, every Tricloud Nexus installation includes an ingestion storage account that is fully managed by the platform. The exact path within the **files-drop** container is determined by your job settings. For example: ``` /files-drop//// ``` {% hint style="info" %} The default storage account use for ingestion of data from all devices can be found in [Platform Settings/Endpoints](https://docs.tricloudnexus.io/management-portal/platform-settings/endpoints). Look for the Endpoint that has type 'Ingestion'. **Note**: The default ingestion storage account can also be configured for each individual device in the [device settings](https://docs.tricloudnexus.io/management-portal/management/device-configuration/settings) {% endhint %} *** ### Example storage location Suppose you have an Edge device named `sesam-device-dallas` and a File Job named `MoveLabFtpFiles`. If you specify a `${deviceid}`token as **Destination Folder,** files will be uploaded to: ``` files-drop/sesam-device-dallas/MoveLabFtpJob/ ``` You can further structure the destination path using **directory tokens** as specified below (e.g., `${deviceid}/$(yyyy)`), which automatically resolve to dynamic values such as the Edge device name, job name, or current date, current year etc. This allows for highly organized and easily searchable cloud file storage. | $(deviceid) | Replace a part of a filepath with the Device Id of the Edge device using the token $(deviceid). |

rootfolder/$(deviceid)/otherfolder

rootfolder/EdgeDevice-1/otherfolder

| | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------ | | $(yyyy) | Replace a part of a filepath with the current Year UTC (Eg. 2021) using the token $(yyyy). |

rootfolder/$(yyyy)/otherfolder

rootfolder/2021/otherfolder

| | $(MM) | Replace a part of a filepath with the current Month UTC (Eg. 01-12) using the token $(MM). |

rootfolder/$(MM)/otherfolder

rootfolder/07/otherfolder

| | $(dd) | Replace a part of a filepath with the current Day of month UTC (Eg. 01-31) using the token $(dd). |

rootfolder/$(dd)/otherfolder

rootfolder/07/otherfolder

| | $(HH) | Replace a part of a filepath with the current UTC hour (Eg. 00-24) using the token $(HH). |

rootfolder/$(HH)/otherfolder

rootfolder/13/otherfolder

| | $(mm) | Replace a part of a filepath with the current UTC minute (Eg. 00-59) using the token $(mm). |

rootfolder/$(mm)/otherfolder

rootfolder/57/otherfolder

| | $(ss) | Replace a part of a filepath with the current UTC Second (Eg. 00-59) using the token $(ss). |

rootfolder/$(ss)/otherfolder

rootfolder/35/otherfolder

| | $(FFF) | Replace a part of a filepath with the current UTC MilliSecond (Eg. 000-999) using the token $(FFF). |

rootfolder/$(FFF)/otherfolder

rootfolder/358/otherfolder

| | $(unixts) | Replace a part of a filepath with the current Unix Timestamp UTC (Number of milliseconds that has elapsed since 1970-01-01) using the token $(unixts). |

rootfolder/$(unixts)/otherfolder

rootfolder/1629098246320/otherfolder

| *** ### How it works * **Automatic Upload:** When the job runs and finds files to process, they are copied or moved to the ingestion storage account in the cloud. * **Reliable Delivery:** Files are buffered and retried automatically if the network is temporarily unavailable. * **Separation of Concerns:** Each device and job writes to its own subfolder, preventing file conflicts and ensuring traceability. #### Best Practices * **Consistent Naming:** Use clear and consistent job and device names to make finding files easy. * **Use Tokens for Dynamic Folders:** Take advantage of folder tokens (such as `${deviceid}`) for automatic organization. * **Monitor Ingestion:** You can track successful uploads and job execution logs from the File Transfer Module or Jobs tab. * **Retention & Processing:** Once in the cloud, files can be processed further by downstream analytics, business intelligence tools, or long-term archiving solutions. #### Summary | Setting in Job | Where files go in cloud | | ---------------------------- | ---------------------------------------------------------------------------- | | No custom folder | files-drop/\/\/\ | | Destination folder: `batch1` | files-drop/\/\/batch1/\ | | With tokens: `${deviceid}` | files-drop/\/\/\/\ | {% hint style="info" %} The default storage account use for ingestion of data from all devices can be found in [Platform Settings/Endpoints](https://docs.tricloudnexus.io/management-portal/platform-settings/endpoints). Look for the Endpoint that has type 'Ingestion'. **Note**: The default ingestion storage account can also be configured for each individual device in the [device settings](https://docs.tricloudnexus.io/management-portal/management/device-configuration/settings) {% endhint %} *** By leveraging Jobs that Send files to cloud, you can ensure that important documents, reports, and measurement files from the Edge are always available, organized, and ready for enterprise-wide access and processing.