Texau logo

Normalize and Deduplicate List (Utility)

Texau → Normalize and Deduplicate List (Utility)

POST/v1/texau-normalize-deduplicate-list
texau__texau-normalize-deduplicate-listenrichment
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/texau-normalize-deduplicate-list
{
  "input": "sample-value"
}
200 Accepted
{
  "ok": true,
  "data": {
    "deduped_list": "sample",
    "deduped_string": "sample",
    "deduplicated_count": 1,
    "original_count": 1
  }
}

Removes duplicate entries from a list of strings and returns unique items.

Install

Add normalize and deduplicate list (utility) to your MCP client.

Drop this into claude_desktop_config.json (or your client's equivalent) and the tool shows up in any chat.

claude_desktop_config.json
{
  "mcpServers": {
    "texau": {
      "command": "npx",
      "args": ["-y", "@texau/mcp-server"],
      "env": { "TEXAU_API_KEY": "..." }
    }
  }
}

Tool name: texau__texau-normalize-deduplicate-list

When to use this.

The "Normalize & Deduplicate List" action is designed to streamline data management by removing duplicate entries from a provided list of strings, ensuring that only unique items are returned. Users input a list of strings through the 'input' parameter, which is essential for the deduplication process. The action outputs a deduplicated list as an array ('deduped_list'), a comma-separated string ('deduped_string'), and counts of both the original and deduplicated entries ('original_count' and 'deduplicated_count'). This action falls under the enrichment category and is particularly useful in scenarios such as data cleaning, preparing datasets for analysis, or enhancing user-generated content by eliminating redundancy. With its focus on text and count data types, this action is ideal for developers and data analysts looking to optimize data integrity and usability.

Try it

Run a sample request.

The response is a deterministic, cached example. No live call, no credits used.

Normalize and Deduplicate List (Utility)

Try it

The list of strings to normalize and deduplicate.

Response is cached — no live API call.

Response

Output schema.

Every field returned in `data`. Click rows to expand nested objects.

FieldType
  • deduped_list
    Deduped List
    nullablearray
  • deduped_string
    Deduped String
    nullabletext
  • deduplicated_count
    Deduplicated Count
    number
  • original_count
    Original Count
    number

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/texau-normalize-deduplicate-list. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/texau-normalize-deduplicate-list
curl -X POST 'https://v3-api.texau.com/api/v1/texau-normalize-deduplicate-list' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"input":"sample-value"}'
200 Accepted
{
  "ok": true,
  "data": {
    "deduped_list": "sample",
    "deduped_string": "sample",
    "deduplicated_count": 1,
    "original_count": 1
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Normalize and Deduplicate List (Utility)→Remove Extra Whitespace (Utility)→Identify Email Type (Utility)

Output

Results land in a TexAu table.

Sample rows below.

Real result preview coming soon.

InputStatusScore
[email protected]valid96
[email protected]risky54
[email protected]invalid12

Workflow

A real example.

Trigger → normalize and deduplicate list (utility) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

Step 1TriggerNew row, webhook, or schedule.
Step 2Normalize and Deduplicate List (Utility)Texau action runs.
Step 3EnrichWaterfall fills missing fields.
Step 4Push to CRMHubSpot / Salesforce / Pipedrive.

Built for

Who runs this.

GTM EngineerRevOpsAgency

Reliability

Rate limits & reliability.

  • Per-minute limit300 / min
  • Per-day limit10,000 / day
  • RetriesAutomatic w/ backoff
  • ModeSync

Errors

HTTP status codes.

What each response means and what to do about it.

CodeCauseFix
200 OKAction ran. Data in `data`.Read response.
400 Bad RequestMissing or malformed input.Validate against the input schema.
401 UnauthorizedMissing or invalid `x-api-key`.Re-issue from /api-platform.
403 ForbiddenWorkspace lacks plan tier.Upgrade or contact sales.
404 Not FoundAction key not recognized.Verify the slug.
429 Rate LimitedPer-minute or per-day cap hit.Backoff; reduce concurrency.
500 Server ErrorUnexpected TexAu issue.Retry with backoff.
502 Bad GatewayUpstream provider 5xx.Retry; we surface root cause.
504 TimeoutUpstream slower than maxLatency.Switch to `isAsync` polling.

Pricing

What it costs to run.

Light tier

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

Related

More Texau actions.

FAQ.

  • Is this real-time?

    Yes. Synchronous actions return in ~1–4 s. Long-running work uses async polling (see status 504 → switch to async).

  • Do I get charged on failure?

    No. Verified failures cost zero credits. Provider miss / 5xx / timeout cascade to the next provider in the waterfall when applicable.

  • Does it work with Claude / Cursor via MCP?

    Yes. Add the texau MCP server to your client config, then call `texau__texau-...` directly.

  • 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 Normalize and Deduplicate List (Utility) in 60 seconds.

Pull your API key, paste the cURL, ship to your CRM.

Start free →Read the API docs