Texau logo

Format Date and Time (Utility)

Texau → Format Date and Time (Utility)

POST/v1/texau-format-date-time
texau__texau-format-date-timeenrichment
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/texau-format-date-time
{
  "date": "sample-value"
}
200 Accepted
{
  "ok": true,
  "data": {
    "applied_locale": "sample",
    "applied_timezone": "sample",
    "day": 1,
    "formatted_date": "sample",
    "full_date_time": "sample",
    "localized_date_time": "sample",
    "localized_date_with_month_name": "sample",
    "localized_date_with_weekday": "sample",
    "localized_short_date": "sample",
    "localized_time": "sample",
    "month_name": "sample",
    "month_number": 1,
    "original_input": "sample",
    "parsed_successfully": true,
    "short_year": 1,
    "time": "sample",
    "unix_timestamp": 1,
    "year": 1
  }
}

Converts a date-time string to UTC timezone and extracts individual date and time components.

Install

Add format date and time (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-format-date-time

When to use this.

The texau-format-date-time action is designed to convert a date-time string into the UTC timezone while extracting essential components such as year, month, day, and time. This action accepts a single input parameter, 'date' (text), which can be in various formats, including ISO 8601 and other common date representations. The output includes a range of fields, such as 'formatted_date' (text), 'localized_date_time' (text), and 'unix_timestamp' (text), providing comprehensive insights into the parsed date-time. This action is particularly useful for applications requiring date-time normalization, such as event scheduling, data analysis, and reporting, making it an essential tool in the enrichment category for developers and data analysts.

Try it

Run a sample request.

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

Format Date and Time (Utility)

Try it

Original date-time input string to parse and format (e.g., ISO 8601, common date formats).

Response is cached — no live API call.

Response

Output schema.

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

FieldType
  • applied_locale
    Applied Locale
    nullabletext
  • applied_timezone
    Applied Timezone
    nullabletext
  • day
    Day
    number
  • formatted_date
    Formatted Date
    text
  • full_date_time
    Full Date Time
    nullabletext
  • localized_date_time
    Localized Date Time
    nullabletext
  • localized_date_with_month_name
    Localized Date With Month Name
    nullabletext
  • localized_date_with_weekday
    Localized Date With Weekday
    nullabletext
  • localized_short_date
    Localized Short Date
    nullabletext
  • localized_time
    Localized Time
    nullabletext
  • month_name
    Month Name
    nullabletext
  • month_number
    Month Number
    nullablenumber
  • original_input
    Original Input
    nullabletext
  • parsed_successfully
    Parsed Successfully
    nullableboolean
  • short_year
    Short Year
    nullablenumber
  • time
    Time
    nullabletext
  • unix_timestamp
    Unix Timestamp
    nullablenumber
  • year
    Year
    number

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/texau-format-date-time. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/texau-format-date-time
curl -X POST 'https://v3-api.texau.com/api/v1/texau-format-date-time' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"date":"sample-value"}'
200 Accepted
{
  "ok": true,
  "data": {
    "applied_locale": "sample",
    "applied_timezone": "sample",
    "day": 1,
    "formatted_date": "sample",
    "full_date_time": "sample",
    "localized_date_time": "sample",
    "localized_date_with_month_name": "sample",
    "localized_date_with_weekday": "sample",
    "localized_short_date": "sample",
    "localized_time": "sample",
    "month_name": "sample",
    "month_number": 1,
    "original_input": "sample",
    "parsed_successfully": true,
    "short_year": 1,
    "time": "sample",
    "unix_timestamp": 1,
    "year": 1
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Format Date and Time (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 → format date and time (utility) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

Step 1TriggerNew row, webhook, or schedule.
Step 2Format Date and Time (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 limit50,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 Format Date and Time (Utility) in 60 seconds.

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

Start free →Read the API docs