> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/connectors-and-triggers/connectors/files/append-files.md). # Append Files Discover more about the Append Files component and how to use it on the Digibee Integration Platform. **Append Files** adds one or more text files to an existing text file. ## Parameters Take a look at the configuration parameters of the component. Parameters supported by [Double Braces expressions](/documentation/connectors-and-triggers/double-braces/overview.md) are marked with `(DB)`.

Parameter	Description	Default value	Data type
File Name `(DB)`	Name of the file or full file path (for example, tmp/processed/file.txt) that receives the content from other files.	N/A	String
Charset	Charset of the final file.	UTF-8	String
Custom Files Specification `(DB)`	If the option is active, it’s possible to inform the files list to the component in a dynamic way.	False	Boolean
Files to Append	If Custom Files Specification is not active, you can add the files to be added to the original file by clicking the +Add button. Otherwise, you can inform the files list in the corresponding field.	N/A	Array of Objects (JSON) or Options of Files to Append
File Name	Name of the file. This parameter is displayed only if Custom Files Specification is not active and after clicking the +Add button.	{{ message.fileName }}	String
Charset	Charset of the file. This parameter is displayed only if Custom Files Specification is not active and after clicking the +Add button.	UTF-8	String
Fail On Error	If the option is active, the execution of the pipeline with error will be interrupted; otherwise, the pipeline execution proceeds, but the result will show a false value for the “success” property.	False	Boolean

## Messages flow ### Input Only the files to be used in this component must be in the current pipeline directory. ### Output ``` { "fileName": "pipeline-example", "success": true } ``` * **fileName:** name of the final file. * **success:** when the call is successful. ## Append Files in Action See below how the component behaves in a determined situation and what its respective configuration is. ### Appending multiple files * **File Name:** final\_file\_final.txt * **Charset:** "UTF-8" * **Custom Append Files Specification:** enabled * **Files to Append:** ``` [ {"fileName": "file1.txt", "charset": "UTF-8"}, {"fileName": "file2.txt", "charset": "UTF-8"} ] ``` * **Fail On Error:** false * **File content:** final\_file.txt ``` HEADER line1 ``` * **File content:** file1.txt ``` file1 test ``` * **File content:** file2.txt ``` file2 another test ``` ### Output ``` { "fileName": "final_file.txt", "success": true } ``` * **Final file content:** final\_file.txt ``` HEADER line1file1 testfile2 another test ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.digibee.com/documentation/connectors-and-triggers/connectors/files/append-files.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.