<!-- BusyBot node reference — https://busybot.net/tools/console-logger/ -->

> Node: Console Logger (`console_logger`) · Action · v1
> Category: Core Nodes · Credentials: none
> Updated: 2026-08-16

# Console Logger

> Log messages for debugging

## Overview

Logs a message to the console with full execution tracking. The message is written to the execution log and the item continues down the workflow, so you can drop the node anywhere in a chain to inspect what is flowing through it. Each forwarded item carries two markers added to its JSON: `logged` (always `"ok"`) and `processedAt` (the epoch-millisecond timestamp of the write).

**Category:** Core Nodes  
**Tool Name:** `console_logger`  
**Version:** 1

**Appearance:** Icon: `terminal` | Color: `#6b7280`

## Node Type

**Action** — processes input items and produces output

## Input / Output

| Direction | Port(s) |
|-----------|--------|
| Input | `Input` |
| Output | `Output`, `Error` |

## Credentials

This tool does not require any credentials.

### Parameters

| Parameter | Type | Required | Default | Description |
|-----------|------|----------|---------|-------------|
| Message | `string` | Yes | `Default log message.` | The message to log. Supports expressions like {{ $json.field }}. |
| Log Level | `options` | No | `log` | The console method to use for logging. |
| | | | | Options: `log`, `warn`, `error`, `info`, `debug` |
| Max Concurrency | `number` | No | `100` | Maximum number of items to process concurrently. |
| Output Empty? | `boolean` | No | `false` | If true, the node will output nothing even if it processed successfully. |

## Output Data

One output item per input item. The item JSON passes through with two markers added — `logged` (always `"ok"`) and `processedAt` (the epoch-millisecond timestamp of the write) — and binary data is forwarded unchanged.

Turning **Output Empty?** on suppresses the output entirely: the messages are still logged, but the node emits no items, which ends that branch of the workflow.

## Usage Examples

- log the current item for debugging
- print the status at this point
- output the response to console
- debug the workflow data
- show what values are being processed

## Example Configuration

Log a message built from the current item:

```json
{
  "type": "console_logger",
  "parameters": {
    "message": "Default log message.",
    "logLevel": "log",
    "maxConcurrency": 100,
    "outputEmpty": false
  }
}
```

### Error Handling

| Mode | Behavior |
|------|----------|
| **stop** | Halts workflow on first error |
| **continue** | Skips failed items, passes successful ones through |
| **errorPort** | Routes failed items to Error output port |

## Tips

Logs input data to the system console for debugging purposes. Use when you need to inspect intermediate data flowing through the pipeline. Produces the same items it received, with two markers added to each item JSON: `logged` and `processedAt`.