> ## Documentation Index
> Fetch the complete documentation index at: https://docs.markifact.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Count List Items

> Count the number of items in any list to track quantities and build conditional logic.

**Count List Items** returns the total number of items in a list. Use this to check list sizes, build conditional logic, or track quantities in your workflows.

***

## When to Use It

* Check how many campaigns were returned from an API call
* Count URLs from sitemap extraction before processing
* Verify list sizes before starting loops
* Build conditional workflows based on quantity thresholds

***

## Inputs

| Field    | Type | Required | Description                           |
| -------- | ---- | -------- | ------------------------------------- |
| **List** | List | Yes      | The list you want to count items from |

***

## Outputs

| Output    | Description                     |
| --------- | ------------------------------- |
| **Count** | The number of items in the list |

***

## Credit Cost

Free to use - no credits required.

***

## Real-World Examples

**Campaign Quantity Check:**

```
Google Ads Get Report → Count List Items → Conditional Split
"If campaign count > 10, send summary email"
```

**URL Processing Validation:**

```
Extract URLs from Sitemap → Count List Items → Create Input Variable
Store count to display in notifications: "Processing 47 URLs"
```

**Batch Size Planning:**

```
Sheets Read Data → Count List Items → Split List
"If client list has 100+ items, split into batches of 25"
```

***

## Tips

**Conditional Logic:**

* Connect the count output to a Conditional Split node to create different workflows based on list size
* Useful for handling empty lists or setting processing limits

**Progress Tracking:**

* Use the count in email notifications to show progress: "Processing 3 of 15 accounts"
* Helps stakeholders understand workflow scope

**Workflow Optimization:**

* Check list sizes before expensive operations
* Skip processing if lists are empty to save resources

***

## FAQ

<Accordion title="What happens if I try to count an empty list?">
  The node will return 0 as the count. This is useful for conditional logic to check if a list has any items before proceeding with processing.
</Accordion>

<Accordion title="Can I use the count in conditional logic?">
  Yes, connect the count output to a Conditional Split node to create different workflow paths. For example, "If count > 50, split into batches" or "If count = 0, send empty list notification".
</Accordion>

<Accordion title="Does this work with all types of lists?">
  Yes, it counts any list regardless of content - URLs, campaign names, numbers, or mixed data types. It simply counts the number of items.
</Accordion>

<Accordion title="How do I use the count for progress tracking?">
  Connect the count to email notifications or input variables to show progress like "Processing 25 of 100 campaigns". Combine with loop counters for real-time updates.
</Accordion>

<Accordion title="What's the maximum number of items it can count?">
  There's no practical limit. The node can count very large lists efficiently, though extremely large lists may take slightly longer to process.
</Accordion>