> 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.1-hello-shopify.md).

# 3.1 🛍️ Hello Shopify

## Scenario: Get All Product Information from Shopify 

{% stepper %}
{% step %}

### Connect to Shopify

Go to your Workflow and search for the system named “Shopify” and select.

<figure><img src="/files/vcsoRF8oZ7NFySjm92om" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Add Credential

Click the drop-down under Select Credentials and click on Add Credentials.&#x20;

Fill up the required credential fields.&#x20;

1. Provide a unique name to easily identify these credentials later.
2. Select the time zone of the system.&#x20;

***Why Time Zone Matters?***

*Different systems may operate in different time zones. For example, one system may use UTC while another uses IST. Knowing the native time zone of the system helps avoid time mismatches when creating, reading, or comparing data. This time zone can be reused later in the workflow while processing data, ensuring time-based data is handled correctly.*

3. Turn on the toggle for Show Credentials on Data Hub only if you want to extract and use the credential value in the workflow.

**Note:** *By default, authorization is handled by DCKAP Integrator even if you do not turn this on. Use this only if you explicitly need a specific value from the selected credential for any step in the workflow.*

4. Enter your Shopify Store Name, Client ID and Client Secret and click on Submit.

<figure><img src="/files/Phh11KTxSK50InDW2FhR" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Choose API

Type Products and choose **Retrieve a List of Products** from the drop-down of APIs and click on Next. Enable Show output in Console Logs and click on the tick icon at the top right. Click on Save.&#x20;
{% endstep %}

{% step %}

### Execute

Click and Sync Now. Click on Logs and View Console.&#x20;

#### 🎉 Congratulations! You have successfully talked to Shopify via DCKAP Integrator.

#### Understanding Response-Based Pathways

After the Shopify API Call step, you will notice two pathways:

Option A: Response is Valid

Option B: Response is Not Valid | API Failed<br>

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

#### Option A: Response is Valid (Success Path)

* This path is followed when the API call is successful.
* By default, success means the API returns a status code of 200.
* Add the steps you want to execute after a successful response under this option.

#### Option B: Response is Not Valid | API Failed (Failure Path)

* This path is followed when the API call fails.
* If the response status is anything other than 200, this path is executed.
* Add steps here to handle errors, retries, or logging.

#### When Are These Options Executed?

* Option A runs → when the API response is successful (status = 200)
* Option B runs → when the API response is not successful
  {% endstep %}
  {% endstepper %}

## Customizing the Conditions

* Go to the Response Validation tab in the step
* Define your own conditions based on response data or status. If you need more conditions:
  * Click Add Option
  * Define additional conditions
  * Route the workflow based on different outcomes

This makes your workflow smart and decision-driven, instead of following a fixed path 👍 You also have the ability to unleash the power of Workflow Variables and Inline Transformation in combination. For more details, check out [this](https://docs.dckapintegrator.com/project-manager/workflows/variables).


---

# 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.1-hello-shopify.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.