Texau logo

Remove Extra Whitespace (Utility)

Texau → Remove Extra Whitespace (Utility)

POST/v1/texau-remove-extra-whitespace
texau__texau-remove-extra-whitespaceenrichment
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/texau-remove-extra-whitespace
{
  "text": "sample-value"
}
200 Accepted
{
  "ok": true,
  "data": {
    "change_applied": true,
    "character_removed": 1,
    "normalized_length": 1,
    "normalized_text": "sample",
    "original_length": 1,
    "original_text": "sample"
  }
}

Cleans up text by removing extra spaces, tabs, and newlines while preserving single spaces.

Install

Add remove extra whitespace (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-remove-extra-whitespace

When to use this.

The "Remove Extra Whitespace" action is designed to enhance text readability by eliminating unnecessary spaces, tabs, and newlines while retaining single spaces. This action takes a single input parameter, "text," which is the raw text requiring normalization. Upon execution, it outputs several key metrics: "changes_applied" indicates whether any modifications were made, "characters_removed" quantifies the number of characters eliminated, "normalized_length" provides the length of the cleaned text, "normalized_text" presents the refined version of the input, "original_length" reflects the length of the initial text, and "original_text" displays the unaltered input. This action falls under the enrichment category and is particularly useful in data preprocessing, content formatting, and improving text clarity for applications such as document editing, web content management, and automated reporting.

Try it

Run a sample request.

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

Remove Extra Whitespace (Utility)

Try it

The input text to normalize by removing extra whitespace.

Response is cached — no live API call.

Response

Output schema.

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

FieldType
  • change_applied
    Change Applied
    nullableboolean
  • character_removed
    Character Removed
    nullablenumber
  • normalized_length
    Normalized Length
    nullablenumber
  • normalized_text
    Normalized Text
    nullabletext
  • original_length
    Original Length
    nullablenumber
  • original_text
    Original Text
    text

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/texau-remove-extra-whitespace. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/texau-remove-extra-whitespace
curl -X POST 'https://v3-api.texau.com/api/v1/texau-remove-extra-whitespace' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"text":"sample-value"}'
200 Accepted
{
  "ok": true,
  "data": {
    "change_applied": true,
    "character_removed": 1,
    "normalized_length": 1,
    "normalized_text": "sample",
    "original_length": 1,
    "original_text": "sample"
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Remove Extra Whitespace (Utility)→Identify Email Type (Utility)→Find URL Redirect Destination (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 → remove extra whitespace (utility) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

Step 1TriggerNew row, webhook, or schedule.
Step 2Remove Extra Whitespace (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 Remove Extra Whitespace (Utility) in 60 seconds.

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

Start free →Read the API docs