> 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/project-manager/workflows/actions.md).

# Actions

Formerly Handlers.

Actions are used to build a flow in a tree structure, left to right. Every action has its functional logic and requires a certain set of inputs to be defined to carry out its activities. Multiple Actions are available to the user to build their flow.

Available actions are

* [API Call](/project-manager/workflows/actions/api-call.md)
* [Console](/project-manager/workflows/actions/console.md)
* [Decision](/project-manager/workflows/actions/decision.md)
* [Loop](/project-manager/workflows/actions/loop.md)
* [Detail Logger](/project-manager/workflows/actions/detail-logger.md)
* [Error Logger](/project-manager/workflows/actions/error-logger.md)
* [Code Runner](/project-manager/workflows/actions/code-runner.md)
* [Formatter](/project-manager/workflows/actions/formatter.md)
* [Notification](/project-manager/workflows/actions/notification.md)
* [Return](/project-manager/workflows/actions/return.md)
* [Sleep](/project-manager/workflows/actions/sleep.md)

### Action/Step Output in Console Logs

Each action/step has an option `Show output in console logs` which allows the users to control each step outputs in console logs. 

* If enabled, the execution status of the action or step output is logged in console logs. 
  * For API calls, users can customize the information in more detail by selecting options such as Request Information, Response Information, and more.
* If disabled, the respective action step output will not be logged in console logs. 

This allows the users to customize the information available in the console logs.

{% hint style="info" %}
This option will only work if console logging is enabled both in the project settings and for the specific pipe or workflow.
{% endhint %}


---

# 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.dckapintegrator.com/project-manager/workflows/actions.md?ask=<question>&goal=<user_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.