Skip to main content
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

FieldTypeRequiredDescription
ListListYesThe list you want to count items from

Outputs

OutputDescription
CountThe 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

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.
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”.
Yes, it counts any list regardless of content - URLs, campaign names, numbers, or mixed data types. It simply counts the number of items.
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.
There’s no practical limit. The node can count very large lists efficiently, though extremely large lists may take slightly longer to process.
I