> 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/2.-hello-workflow/2.1-lets-run-your-first-workflow.md).

# 2.1 ▶️ Let’s Run Your First Workflow

{% stepper %}
{% step %}

### 🧩 Add Your First Step

Head over to the Workflow page.\
Here, you’ll see options like Tools and Systems—these are building blocks for your workflow.

For now, let’s keep it simple:

* Choose Console under Tools

💡 What is Console?\
Think of it as a place where you can print or log messages—just like a “Hello World” when learning programming.

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

{% endstep %}

{% step %}

### ✍️ Configure the Step

You’ll see a Message field. Enter **My First Workflow** and Click the ✔ (tick icon) to confirm

✅ What you just did:\
You created a simple step that will log a message when the workflow runs.

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

<br>
{% endstep %}

{% step %}

### 💾 Save Your Workflow

Don’t forget to click Save Workflow. This ensures your setup is stored before running it.

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

<br>
{% endstep %}

{% step %}

### ⚙️ Enable Console Logs

Now, let’s make sure you can actually see the output.

* Click Settings (top right)
* Turn ON the Console Log toggle

⚠️ **Common Situation (One-Time Setup Step):**\
You might see a message saying Console Logs are disabled for the project.

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

👉 Here’s how to fix it:

1. Go to Project Settings (left menu)&#x20;

<figure><img src="/files/2eu2PAMS9dELegug0i9K" alt=""><figcaption></figcaption></figure>

2. Under General Settings, enable Console Logs by choosing Yes
3. Click Save

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

\
Now come back to the Workflow Page by choosing Workflows  from the left navigation menu and Edit your Workflow. Turn ON the Console Log toggle again in Settings.

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

<br>
{% endstep %}

{% step %}

### ▶️  Run the Workflow

Click Sync Now at the top right.

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

#### 🎉 Hooray! You’ve just run your first workflow!

{% endstep %}

{% step %}

### 🔍 View/Download Your Output

Now let’s check the result. Click View Console.

👉 The button is visible for 10 seconds. Don’t see it now? Click Logs. There, you’ll find the View Console button. Click on it.<br>

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

You have the ability to download the log as well.

✅ **What you should see:**\
Your message: “**My First Workflow**” printed in the console.

<br>
{% endstep %}
{% endstepper %}

<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/2.-hello-workflow/2.1-lets-run-your-first-workflow.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.
