--- alias: user-guide-automation-task-opcua-createfile tags: - automation tasks description: "This documentation describes creating a file on an OPC UA server using a driver" --- # Create File ![Screenshot showing a file creation interface.](images/createfile-lg.svg) This task creates a file in OPC UA server using the File Transfer feature. To be used with OPC UA driver in Client mode. ![Screenshot showing a UI with options to create a file, including "Node ID" and "File Name".](./images/create_file_parameters.png) ## Inputs | Name | Data Type | Description | | ------ | ---------| ------------------------------------------ | | nodeId | `String` | The node id where the file will be created | | name | `String` | Name for the file | | Activate | `any` | Activate the task | ## Outputs | Name | Data Type | Description | | ---------- | --------- | ----------------------------------------------------------------------- | | fileNodeId | `String` | The newly created node id for the file | | isNew | `Boolean` | The flag that specifies whether the file was created or already existed | | Success | `Boolean` | If there was no problem emits a true | | Error | `Error` | Error that occurred during the processing of this task | ## Settings On the *General Tab*, you have the usual settings and the following settings: | Name | Data Type | Default | Description | | -------------- | --------- | --------- | ---------------------------------------------------------------------------------------------------- | | NodeId | `String` | | The node id where the file will be created | | Fail if exists | `Boolean` | False | If true and the file exists, will throw an error, otherwise will output the already existing node id | ![Diagram showing a table with columns labeled "Name", "Data Type", and "Default".](./images/create_file_settings.png) ## Behavior Activate will trigger a message to the driver. The contents of the message are the values received in the inputs or settings. ## Remarks All the communication with the equipment is handled by the driver in the backend.