Smartlead logo

Update Campaign Lead (Smartlead)

SmartleadUpdate Campaign Lead (Smartlead)

POST/v1/smartlead-update-campaign-lead
texau__smartlead-update-campaign-leadintegration
cURL · api.texau.app
84ms
POST/v1/smartlead-update-campaign-lead
{
  "campaign_id": "sample-value",
  "lead_id": "sample-value",
  "first_name": "Jane",
  "last_name": "Doe",
  "email": "[email protected]",
  "mobile_number": "sample-value",
  "company_name": "Acme, Inc.",
  "website": "https://acme.com",
  "location": "sample-value",
  "linkedin_url": "https://acme.com",
  "company_url": "https://acme.com"
}
200 Accepted
{
  "ok": true,
  "data": {
    "ok": true
  }
}

Update details for a specific lead within a Smartlead campaign.

Install

Add update campaign lead (smartlead) 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__smartlead-update-campaign-lead

When to use this.

The "smartlead-update-campaign-lead" action allows users to update the details of a specific lead within a Smartlead campaign, enhancing lead management and engagement. Key input parameters include "campaign_id" and "lead_id," which uniquely identify the campaign and lead, respectively. Additional optional fields such as "first_name," "last_name," "email," "phone_number," "company_name," "website," "location," and "linkedin_profile" enable comprehensive updates to the lead's information. The action outputs a boolean "ok" indicating the success of the request. This functionality is essential for businesses looking to maintain accurate lead data, improve communication strategies, and optimize marketing efforts within integrated systems. Ideal for marketing teams and CRM integrations, this action falls under the integration category and supports various semantic data types including text, email, and ID.

Try it

Run a sample request.

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

Update Campaign Lead (Smartlead)

Try it

Unique identifier of the Smartlead campaign.

Unique identifier of the lead (e.g., email or database ID depending on setup).

Lead's first name.

Lead's last name.

Lead's email address.

Lead's phone number.

Response is cached — no live API call.

Response

Output schema.

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

FieldType
  • ok
    Ok
    boolean

Integrate

Copy-pasteable snippets.

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

cURL · api.texau.app
84ms
POST/v1/smartlead-update-campaign-lead
curl -X POST 'https://v3-api.texau.com/api/v1/smartlead-update-campaign-lead' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"campaign_id":"sample-value","lead_id":"sample-value","first_name":"Jane","last_name":"Doe","email":"[email protected]","mobile_number":"sample-value","company_name":"Acme, Inc.","website":"https://acme.com","location":"sample-value","linkedin_url":"https://acme.com","company_url":"https://acme.com"}'
200 Accepted
{
  "ok": true,
  "data": {
    "ok": true
  }
}

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

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

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