Reply logo

Update Contact (Reply.io)

ReplyUpdate Contact (Reply.io)

POST/v1/reply-update-contact
texau__reply-update-contactcrm
cURL · api.texau.app
84ms
POST/v1/reply-update-contact
{
  "email": "[email protected]",
  "first_name": "Jane",
  "last_name": "Doe",
  "company": "Acme, Inc.",
  "title": "sample-value",
  "mobile_number": "sample-value",
  "city": "sample-value",
  "state": "sample-value",
  "country": "sample-value",
  "time_zone_id": "sample-value",
  "linkedin_url": "https://acme.com"
}
200 Accepted
{
  "ok": true,
  "data": {
    "id": "rec_4f3a91",
    "email": "[email protected]",
    "first_name": "sample",
    "last_name": "sample",
    "company": "sample",
    "title": "sample",
    "mobile_number": "sample",
    "mobile_number_status": "valid",
    "city": "sample",
    "state": "sample",
    "country": 1,
    "time_zone_id": "rec_4f3a91",
    "linkedin_url": "https://acme.com",
    "adding_date": "sample",
    "company_size": "sample",
    "industry": "sample",
    "sales_navigator_url": "https://acme.com",
    "linkedin_recruiter_url": "https://acme.com",
    "account_id": 1
  }
}

Update an existing contact in Reply.io based on their email address

Install

Add update contact (reply.io) 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__reply-update-contact

When to use this.

The "Update Contact (Reply.io)" action allows users to efficiently update existing contacts in the Reply.io CRM system using their email address. This action supports an "upsert" functionality, meaning if the specified email does not exist, a new contact will be created. Key input parameters include the required email address, along with optional fields such as first name, last name, company name, job title, phone number, city, state, country, time zone ID, and LinkedIn profile URL. The output provides comprehensive contact details, including contact ID, email, names, company information, phone status, and relevant URLs. This action is ideal for sales and marketing professionals looking to maintain accurate and up-to-date contact records, enhancing customer relationship management and outreach efforts. It falls under the CRM category, making it essential for businesses aiming to streamline their contact management processes.

Try it

Run a sample request.

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

Update Contact (Reply.io)

Try it

The email address of the contact to update (Required to identify the contact).

First name of the contact.

Last name of the contact.

Name of the company.

Job title or position.

Phone number.

Response is cached — no live API call.

Response

Output schema.

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

FieldType
  • id
    Id
    number
  • email
    Email
    string
  • first_name
    First Name
    string
  • last_name
    Last Name
    string
  • company
    Company
    string
  • title
    Title
    string
  • mobile_number
    Mobile Number
    nullablestring
  • mobile_number_status
    Mobile Number Status
    nullablestring
  • city
    City
    nullablestring
  • state
    State
    nullablestring
  • country
    Country
    nullablestring
  • time_zone_id
    Time Zone Id
    nullablestring
  • linkedin_url
    Linkedin Url
    string
  • adding_date
    Adding Date
    nullablestring
  • company_size
    Company Size
    nullablestring
  • industry
    Industry
    nullablestring
  • sales_navigator_url
    Sales Navigator Url
    nullablestring
  • linkedin_recruiter_url
    Linkedin Recruiter Url
    nullablestring
  • account_id
    Account Id
    nullablenumber

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/reply-update-contact. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/reply-update-contact
curl -X POST 'https://v3-api.texau.com/api/v1/reply-update-contact' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"email":"[email protected]","first_name":"Jane","last_name":"Doe","company":"Acme, Inc.","title":"sample-value","mobile_number":"sample-value","city":"sample-value","state":"sample-value","country":"sample-value","time_zone_id":"sample-value","linkedin_url":"https://acme.com"}'
200 Accepted
{
  "ok": true,
  "data": {
    "id": "rec_4f3a91",
    "email": "[email protected]",
    "first_name": "sample",
    "last_name": "sample",
    "company": "sample",
    "title": "sample",
    "mobile_number": "sample",
    "mobile_number_status": "valid",
    "city": "sample",
    "state": "sample",
    "country": 1,
    "time_zone_id": "rec_4f3a91",
    "linkedin_url": "https://acme.com",
    "adding_date": "sample",
    "company_size": "sample",
    "industry": "sample",
    "sales_navigator_url": "https://acme.com",
    "linkedin_recruiter_url": "https://acme.com",
    "account_id": 1
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

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 → update contact (reply.io) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

Step 1TriggerNew row, webhook, or schedule.
Step 2Update Contact (Reply.io)Reply 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 limitNo public cap
  • Per-day limitPlan-defined
  • 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__reply-...` 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 Update Contact (Reply.io) in 60 seconds.

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