Local File Sink

Class: LocalFileSinkBlockV1

Source: inference.core.workflows.core_steps.sinks.local_file.v1.LocalFileSinkBlockV1

The Local File Sink block saves workflow data as files on a local file system. It allows users to configure how the data is stored, either:

• aggregating multiple entries into a single file

• or saving each entry as a separate file.

This block is useful for logging, data export, or preparing files for subsequent processing.

File Content, File Type and Output Mode

content is expected to be the output from another block producing string values of specific types denoted by file_type.

output_mode set into append_log will make the block appending single file with consecutive entries passed to content input up to max_entries_per_file. In this mode it is important that

file_type in append_log mode

Contrary to separate_files output mode, append_log mode may introduce subtle changes into the structure of the content to properly append it into existing file, hence setting proper file_type is crucial:

• file_type=json: in append_log mode, the block will create *.jsonl file in JSON Lines format - for that to be possible, each JSON document will be parsed and dumped to ensure that it will fit into single line.

• file_type=csv: in append_log mode, the block will deduct the first line from the content (making it required for CSV content to always be shipped with header row) of consecutive updates into the content of already created file.

Security considerations

The block has an ability to write to the file system. If you find this unintended in your system, you can disable the block setting environmental variable ALLOW_WORKFLOW_BLOCKS_ACCESSING_LOCAL_STORAGE=False in the environment which host Workflows Execution Engine.

If you want to restrict the directory which may be used to write data - set environmental variable WORKFLOW_BLOCKS_WRITE_DIRECTORY to the absolute path of directory which you allow to be used.

Type identifier

Use the following identifier in step "type" field: roboflow_core/local_file_sink@v1to add the block as as step in your workflow.

Properties

Name	Type	Description	Refs
name	str	Enter a unique identifier for this step..	❌
file_type	str	Type of the file.	❌
output_mode	str	Decides how to organise the content of the file.	❌
target_directory	str	Target directory.	✅
file_name_prefix	str	File name prefix.	✅
max_entries_per_file	int	Defines how many datapoints can be appended to a single file.	✅

The Refs column marks possibility to parametrise the property with dynamic values available in workflow runtime. See Bindings for more info.

Available Connections

Compatible Blocks

Check what blocks you can connect to Local File Sink in version v1.

• inputs: Keypoint Detection Model, CogVLM, Anthropic Claude, OpenAI, Google Vision OCR, Florence-2 Model, Single-Label Classification Model, OpenAI, Object Detection Model, Instance Segmentation Model, Florence-2 Model, Model Monitoring Inference Aggregator, Stitch OCR Detections, VLM as Detector, Roboflow Dataset Upload, Roboflow Dataset Upload, Email Notification, CSV Formatter, LMM, Llama 3.2 Vision, Multi-Label Classification Model, Twilio SMS Notification, Google Gemini, Roboflow Custom Metadata, Clip Comparison, Slack Notification, VLM as Classifier, OpenAI, Webhook Sink, OCR Model, LMM For Classification, Local File Sink
• outputs: Keypoint Detection Model, CogVLM, Anthropic Claude, Cache Set, Gaze Detection, Google Vision OCR, OpenAI, Detections Classes Replacement, Florence-2 Model, Distance Measurement, Pixelate Visualization, Single-Label Classification Model, OpenAI, Stability AI Image Generation, YOLO-World Model, Mask Visualization, Object Detection Model, Triangle Visualization, Path Deviation, Polygon Zone Visualization, Model Comparison Visualization, Crop Visualization, Classification Label Visualization, LMM, Segment Anything 2 Model, Keypoint Detection Model, Reference Path Visualization, Multi-Label Classification Model, Twilio SMS Notification, Line Counter, Google Gemini, Bounding Box Visualization, Roboflow Custom Metadata, Size Measurement, Circle Visualization, Perspective Correction, Slack Notification, Pixel Color Count, Polygon Visualization, Instance Segmentation Model, Trace Visualization, Webhook Sink, Color Visualization, Detections Consensus, LMM For Classification, Image Threshold, Detections Stitch, SIFT Comparison, Line Counter Visualization, Multi-Label Classification Model, Line Counter, Dot Visualization, Dynamic Zone, Instance Segmentation Model, Background Color Visualization, Florence-2 Model, Model Monitoring Inference Aggregator, Template Matching, Roboflow Dataset Upload, Roboflow Dataset Upload, Time in Zone, Image Blur, Email Notification, Path Deviation, Object Detection Model, Label Visualization, Blur Visualization, CLIP Embedding Model, Stability AI Inpainting, Llama 3.2 Vision, Image Preprocessing, Ellipse Visualization, ONVIF Control, Halo Visualization, Corner Visualization, Clip Comparison, Cache Get, Time in Zone, Dynamic Crop, Single-Label Classification Model, OpenAI, Keypoint Visualization, Local File Sink

Input and Output Bindings

The available connections depend on its binding kinds. Check what binding kinds Local File Sink in version v1 has.

Bindings

• input

  • content (string): Content of the file to save.
  • target_directory (string): Target directory.
  • file_name_prefix (string): File name prefix.
  • max_entries_per_file (string): Defines how many datapoints can be appended to a single file.

• output

  • error_status (boolean): Boolean flag.
  • message (string): String value.

Example JSON definition of step Local File Sink in version v1

{
    "name": "<your_step_name_here>",
    "type": "roboflow_core/local_file_sink@v1",
    "content": "$steps.csv_formatter.csv_content",
    "file_type": "csv",
    "output_mode": "append_log",
    "target_directory": "some/location",
    "file_name_prefix": "my_file",
    "max_entries_per_file": 1024
}