> For the complete documentation index, see [llms.txt](https://docs.dckapintegrator.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dckapintegrator.com/tutorials/workflow-builder-tutorial/3.-hello-system/3.6-lets-log-details.md).

# 3.6 📋 Let's Log Details

Use Detailed Log tool to track successful and failed product syncs to Shopify, so your team can identify and retry failed records.

**Step 1: Initialize Product Data**

Create a new batch workflow and initialize a variable called products:

JSON

```
[
  {"title": "Laptop"},
  {"name": "PROD-002"},
  {"title": "Keyboard"}
]
```

**Step 2: Add a Loop**

Add a Loop step with the following configuration:

* Loop Type — Select Loop through values
* Iterable — Place your cursor in the Iterable field, open the Data Hub, and select variables → products

The syntax will be: {{variables.products}}

**Step 3: Connect to Shopify (Inside Loop)**

Inside the Loop, add an API Call step to connect to your Shopify store and call the Create a New Product API. In the payload section, configure the following:

```
{
  "product": {{1.item}}
}
```

**Step 4: Configure Response Validation**

In the Response Validation section of the API Call step, you will see two pathways — Valid Response and Else.

By default, the valid response checks for status code 200. Change this to 201 because Shopify returns 201 when a product is created successfully.

<figure><img src="/files/cBdjC3j4hxxJzAY26O01" alt=""><figcaption></figcaption></figure>

**Step 5: In the Valid Response Pathway, Add Detailed Log (Success)**

Add a Detailed Log tool in the Valid Response pathway and configure it:

* Status — Success
* Entity ID — {{2.response.product.id}}
* Short Message — {{2.response.product.title}} created successfully
* Update Counters — Check this box

<figure><img src="/files/AHJYyyoeTfwt3A8C47A4" alt=""><figcaption></figcaption></figure>

**Step 6: In the Else Pathway, Add Detailed Log (Failure)**

Add a Detailed Log tool in the Else pathway and configure it:

* Status — Failure
* Entity ID — {{2.meta.request\_payload.product.title}}
* Short Message — {{2.meta.request\_payload.product.title}} creation failed
* Update Counters — Check this box

<figure><img src="/files/kRjx9FENbflZidl7gmf0" alt=""><figcaption></figcaption></figure>

**Step 7: Final Settings and Run**

* Enable Show Output for all steps
* Enable Console Logs for all steps and for the workflow
* Save the workflow
* Click Sync Now

Check the logs to see which products were created successfully and which ones failed. The success and failure counters will show you the total count of records processed.

#### 🎉 Good Job! You have successfully used the Detailed Log tool to track your workflow execution!

***

<br>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.dckapintegrator.com/tutorials/workflow-builder-tutorial/3.-hello-system/3.6-lets-log-details.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
