---
category: [Administration & Integrations, Administration & Integrations/Custom Integrations & Apps, Platform and Product Extensions, Platform and Product Extensions/Integration]
keyword: [Extend, Orchestration Builder, Orchestrate, Orchestration]
nav: wcp_docs
parent_url: /wcp_docs/
title: >- 
  Reference: Log to File
layout: subsection
---

## Purpose

Use this component to store a log as a CSV document that's available to other users and, optionally, can be viewed in the tenant as an attachment to the integration event.

## <a id="section_2"></a>Template Availability

This component is available in these orchestration templates:

-   Integration System


## <a id="section_1"></a>Properties

Provide a meaningful <b>Reference Name</b> for the step as it will appear in your orchestration.

In the <b>Log Name</b> field, use Expression Builder to provide a name for the log file.

You can use the <b>Condition</b> field to optionally specify a condition under which the log file is created. If the condition isn't met, no log file is created.

Orchestration Builder enables you to create resuable CSV formats for log files. In a CSV format, you can specify your own column titles as well as separator, escape, and quote characters. See [Create CSV Formats](/wcp_docs/GUID-982de8c7-ef1e-47e9-9902-8b3cf56d7431.html). To select a format you've previously created, use the <b>Format</b> drop-down list.

If you select a predefined template, the <b>Log</b> section displays the columns you defined for it. Use Expression Builder to provide a <b>Value</b> for each <b>Column</b>.

If you don't select a predefined template, the default columns are:

-   Timestamp
-   Severity
-   Message
-   Details


The default special characters are:

-   Separator (used to separate columns): `,`
-   Escape (used to escape column separators used in fields): `/`
-   Quote (used to enclose other structuring characters): `"`


<b>Note:</b> If an orchestration step fails and isn’t covered by an error handler, Orchestrate automatically stores all named logs and attaches them to the integration event. This means that any logs stored before the step failure are stored again. It doesn’t mean that the relevant steps executed twice.