Extract logo

Extract URLs and Emails (Utility)

Extract → Extract URLs and Emails (Utility)

POST/v1/extract-urls-emails-texau
texau__extract-urls-emails-texauutility
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/extract-urls-emails-texau
{
  "input_text": "sample-value"
}
200 Accepted
{
  "ok": true,
  "data": {
    "email_count": "[email protected]",
    "email": "[email protected]",
    "url_count": "https://acme.com",
    "url": "https://acme.com"
  }
}

Extracts all email addresses and web URLs from a block of text with count summaries.

Install

Add extract urls and emails (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__extract-urls-emails-texau

When to use this.

Extracts all email addresses and web URLs from a block of text with count summaries.

Try it

Run a sample request.

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

Extract URLs and Emails (Utility)

Try it

The text content from which to extract emails and URLs.

Response is cached — no live API call.

Response

Output schema.

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

FieldType
  • email_count
    Email Count
    number
  • email
    Email
    array
  • url_count
    Url Count
    number
  • url
    Url
    array

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/extract-urls-emails-texau. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/extract-urls-emails-texau
curl -X POST 'https://v3-api.texau.com/api/v1/extract-urls-emails-texau' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"input_text":"sample-value"}'
200 Accepted
{
  "ok": true,
  "data": {
    "email_count": "[email protected]",
    "email": "[email protected]",
    "url_count": "https://acme.com",
    "url": "https://acme.com"
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Extract URLs and Emails (Utility)→Enrich→Push to CRM

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 → extract urls and emails (utility) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

Step 1TriggerNew row, webhook, or schedule.
Step 2Extract URLs and Emails (Utility)Extract 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.

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__extract-...` 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 Extract URLs and Emails (Utility) in 60 seconds.

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

Start free →Read the API docs