<!-- BusyBot node reference — https://busybot.net/tools/no-op/ -->

> Node: No Operation, do nothing (`no_op`) · Action · v1
> Category: Core Nodes · Credentials: none
> Updated: 2026-08-16

# No Operation, do nothing

> Pass items through without changes

## Overview

The No Operation (no_op) tool is a passthrough node that takes input items and outputs them without modification. Useful as a placeholder, for workflow organization, or to merge multiple branches without transforming data.

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

**Appearance:** Icon: `lucide-ArrowRight` | Color: `#b0b0b0`

## 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 |
|-----------|------|----------|---------|-------------|
| Max Concurrency | `number` | No | `10` | Maximum number of items to process concurrently. |

## Output Data

One output item per input item, identical to the input. The item JSON is passed through unchanged and binary data is forwarded, so a file attached upstream is still attached downstream. No fields are added or removed.

Because several branches can be wired into the same input, this node also works as a join point: every item arriving on any incoming connection leaves on `Output`.

## Usage Examples

- Use as a merge point for multiple branches
- Placeholder node during workflow development

## Example Configuration

```json
{
  "type": "no_op",
  "parameters": {
    "maxConcurrency": 10
  }
}
```

### 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

Passes items through unchanged — use as a placeholder or branch merge point.