Instantly logo

Update Lead (Instantly)

InstantlyUpdate Lead (Instantly)

POST/v1/instantly-update-lead
texau__instantly-update-leadcrm
cURL · api.texau.app
84ms
POST/v1/instantly-update-lead
{
  "lead_id": "sample-value",
  "email": "[email protected]",
  "first_name": "Jane",
  "last_name": "Doe",
  "company_name": "Acme, Inc.",
  "website": "https://acme.com",
  "mobile_number": "sample-value",
  "personalization": "sample-value",
  "lt_interest_status": 1,
  "pl_value_lead": "sample-value",
  "assigned_to": "sample-value",
  "custom_variable": "sample-value"
}
200 Accepted
{
  "ok": true,
  "data": {
    "id": "rec_4f3a91",
    "company_domain": "https://acme.com",
    "company_name": "sample",
    "email": "[email protected]",
    "first_name": "sample",
    "last_name": "sample",
    "mobile_number": "sample",
    "website": "https://acme.com",
    "personalization": "sample",
    "lt_interest_status": "valid",
    "status": "valid",
    "organization": "sample",
    "timestamp_created": "sample",
    "timestamp_updated": "sample",
    "email_click_count": "[email protected]",
    "email_open_count": "[email protected]",
    "email_reply_count": "[email protected]",
    "esp_code": 1,
    "upload_method": "sample"
  }
}

Update an existing lead in Instantly by ID and return the full updated lead record.

Install

Add update lead (instantly) 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__instantly-update-lead

When to use this.

The "Update Lead (Instantly)" action allows users to efficiently update an existing lead's information in the Instantly CRM by providing a unique lead ID. Key input parameters include optional fields such as email, first name, last name, company name, website, phone number, and personalization notes, enabling tailored updates to each lead's profile. Upon execution, the action returns a comprehensive lead record, including updated fields like company domain, interest status, and engagement metrics such as email click and open counts. This functionality is essential for sales and marketing teams looking to maintain accurate lead information, enhance customer engagement, and streamline communication efforts. The action falls under the CRM category, making it a vital tool for managing customer relationships effectively.

Try it

Run a sample request.

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

Update Lead (Instantly)

Try it

Unique identifier of the lead to update.

Email address of the lead.

First name of the lead.

Last name of the lead.

The company name associated with the lead.

Website URL associated with the lead or company.

Response is cached — no live API call.

Response

Output schema.

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

FieldType
  • id
    Id
    string
  • company_domain
    Company Domain
    nullablestring
  • company_name
    Company Name
    string
  • email
    Email
    string
  • first_name
    First Name
    string
  • last_name
    Last Name
    string
  • mobile_number
    Mobile Number
    nullablestring
  • website
    Website
    string
  • personalization
    Personalization
    nullabletext
  • lt_interest_status
    Lt Interest Status
    nullablenumber
  • status
    Status
    number
  • organization
    Organization
    nullablestring
  • timestamp_created
    Timestamp Created
    nullablestring
  • timestamp_updated
    Timestamp Updated
    nullablestring
  • email_click_count
    Email Click Count
    nullablenumber
  • email_open_count
    Email Open Count
    nullablenumber
  • email_reply_count
    Email Reply Count
    nullablenumber
  • esp_code
    Esp Code
    nullablenumber
  • upload_method
    Upload Method
    nullablestring

Integrate

Copy-pasteable snippets.

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

cURL · api.texau.app
84ms
POST/v1/instantly-update-lead
curl -X POST 'https://v3-api.texau.com/api/v1/instantly-update-lead' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"lead_id":"sample-value","email":"[email protected]","first_name":"Jane","last_name":"Doe","company_name":"Acme, Inc.","website":"https://acme.com","mobile_number":"sample-value","personalization":"sample-value","lt_interest_status":1,"pl_value_lead":"sample-value","assigned_to":"sample-value","custom_variable":"sample-value"}'
200 Accepted
{
  "ok": true,
  "data": {
    "id": "rec_4f3a91",
    "company_domain": "https://acme.com",
    "company_name": "sample",
    "email": "[email protected]",
    "first_name": "sample",
    "last_name": "sample",
    "mobile_number": "sample",
    "website": "https://acme.com",
    "personalization": "sample",
    "lt_interest_status": "valid",
    "status": "valid",
    "organization": "sample",
    "timestamp_created": "sample",
    "timestamp_updated": "sample",
    "email_click_count": "[email protected]",
    "email_open_count": "[email protected]",
    "email_reply_count": "[email protected]",
    "esp_code": 1,
    "upload_method": "sample"
  }
}

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

Step 1TriggerNew row, webhook, or schedule.
Step 2Update Lead (Instantly)Instantly 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__instantly-...` 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 Lead (Instantly) in 60 seconds.

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