Documentation Guidelines

Block Documentation Manual Sections

When updating manual sections (

<!-- MANUAL: ... -->

) in block documentation files (e.g.,

docs/integrations/basic.md

), follow these formats:

How It Works Section

Provide a technical explanation of how the block functions:

Describe the processing logic in 1-2 paragraphs
Mention any validation, error handling, or edge cases
Use code examples with backticks when helpful (e.g.,
```
[[1, 2], [3, 4]]
```
becomes
```
[1, 2, 3, 4]
```
)

Example:

<!-- MANUAL: how_it_works -->
The block iterates through each list in the input and extends a result list with all elements from each one. It processes lists in order, so `[[1, 2], [3, 4]]` becomes `[1, 2, 3, 4]`.

The block includes validation to ensure each item is actually a list. If a non-list value is encountered, the block outputs an error message instead of proceeding.
<!-- END MANUAL -->

Use Case Section

Provide 3 practical use cases in this format:

Bold Heading: Short one-sentence description

Example:

<!-- MANUAL: use_case -->
**Paginated API Merging**: Combine results from multiple API pages into a single list for batch processing or display.

**Parallel Task Aggregation**: Merge outputs from parallel workflow branches that each produce a list of results.

**Multi-Source Data Collection**: Combine data collected from different sources (like multiple RSS feeds or API endpoints) into one unified list.
<!-- END MANUAL -->

Style Guidelines

Keep descriptions concise and action-oriented
Focus on practical, real-world scenarios
Use consistent terminology with other blocks
Avoid overly technical jargon unless necessary

Documentation Guidelines

Block Documentation Manual Sections

When updating manual sections (

<!-- MANUAL: ... -->

) in block documentation files (e.g.,

docs/integrations/basic.md

), follow these formats:

How It Works Section

Provide a technical explanation of how the block functions:

Describe the processing logic in 1-2 paragraphs
Mention any validation, error handling, or edge cases
Use code examples with backticks when helpful (e.g.,
```
[[1, 2], [3, 4]]
```
becomes
```
[1, 2, 3, 4]
```
)

Example:

<!-- MANUAL: how_it_works -->
The block iterates through each list in the input and extends a result list with all elements from each one. It processes lists in order, so `[[1, 2], [3, 4]]` becomes `[1, 2, 3, 4]`.

The block includes validation to ensure each item is actually a list. If a non-list value is encountered, the block outputs an error message instead of proceeding.
<!-- END MANUAL -->

Use Case Section

Provide 3 practical use cases in this format:

Bold Heading: Short one-sentence description

Example:

<!-- MANUAL: use_case -->
**Paginated API Merging**: Combine results from multiple API pages into a single list for batch processing or display.

**Parallel Task Aggregation**: Merge outputs from parallel workflow branches that each produce a list of results.

**Multi-Source Data Collection**: Combine data collected from different sources (like multiple RSS feeds or API endpoints) into one unified list.
<!-- END MANUAL -->

Style Guidelines

Keep descriptions concise and action-oriented
Focus on practical, real-world scenarios
Use consistent terminology with other blocks
Avoid overly technical jargon unless necessary

Documentation Guidelines

Additional Files (1)

Documentation Guidelines

Block Documentation Manual Sections

How It Works Section

Use Case Section

Style Guidelines

Related Skills

<h1 align="center">

2. Apply Deepthink Protocol (reason about dependencies

- Identify gaps

Additional Files (1)

Documentation Guidelines

Block Documentation Manual Sections

How It Works Section

Use Case Section

Style Guidelines