Count logo

Count Item Occurrences (Utility)

Count → Count Item Occurrences (Utility)

count-item-occurrencesenrichmentReturns in seconds

Counts the frequency of each unique item in a string array with totals.

Input

What it needs.

Map each field to a column in your table. Optional fields can stay empty.

FieldType
  • input
    The array of items (strings) to count occurrences for.
    text

When to use this.

The "Count Item Occurrences" action is a utility designed to analyze a string array and determine the frequency of each unique item within it. By providing an input parameter, "input," which is the array of items to be evaluated, users can efficiently obtain insights into item distribution. The action outputs several key fields: "result," a summary of the findings; "result_item," which specifies each unique item; "result_count," indicating the number of occurrences for each item; along with "total_item," the overall count of items processed, and "unique_item," the count of distinct items identified. This action falls under the enrichment category and is particularly useful in data analysis, reporting, and text processing scenarios where understanding item frequency is essential for decision-making and insights generation.

Output

What it returns.

Every field this action writes back to the row. Click a line to expand nested objects.

FieldType
  • result
    Result
    nullablearray
  • result_item
    Result Item
    nullabletext
  • result_count
    Result Count
    text
  • total_item
    Total Item
    number
  • unique_item
    Unique Item
    number

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Count Item Occurrences (Utility)→Enrich→Push to CRM

Workflow

A real example.

Trigger → count item occurrences (utility) → enrich → push to your CRM. You set it up once; after that it runs without you.

Step 1TriggerNew row, form submit, or schedule.
Step 2Count Item Occurrences (Utility)The Count action runs.
Step 3EnrichWaterfall fills missing fields.
Step 4Push to CRMHubSpot / Salesforce / Pipedrive.

Built for

Who runs this.

GTM EngineerRevOpsAgency

Reliability

Throughput & reliability.

How fast it drains a table, and what happens when the upstream provider has a bad day.

  • Per-minute limit300 / min
  • Per-day limit10,000 / day
  • RetriesAutomatic w/ backoff
  • Failed lookupsZero credits

Pricing

What it costs to run.

Light tier

Pricing tier on /pricing. Per-action credit cost is private.

FAQ.

  • Is this real-time?

    Mostly. Fast actions fill the cell in a few seconds. Long-running ones run in the background and write back to the row when they finish, so you can close the tab.

  • Do I get charged on failure?

    No. A failed lookup costs zero credits. When a provider misses or times out, the waterfall moves to the next one and you only pay for the match you actually got.

  • Do I have to run it row by row?

    No. Run it on one cell, on a selection, on the whole table, or on a schedule. Same action either way.

  • What CRMs can I push results to?

    HubSpot, Salesforce, Pipedrive, Zoho, and GoHighLevel are bidirectional. Smartlead, Instantly, Lemlist, HeyReach, Apollo Sequences, and Reply.io for outbound.

Run Count Item Occurrences (Utility) in 60 seconds.

Connect the account, drop the action on a column, run it on your rows.