Reply logo

Create Contact and Push to Campaign (Reply.io)

Reply → Create Contact and Push to Campaign (Reply.io)

POST/v1/reply-push-contact-to-campaign
texau__reply-push-contact-to-campaignintegration
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/reply-push-contact-to-campaign
{
  "campaign_id": "sample-value",
  "email": "[email protected]",
  "first_name": "Jane"
}
200 Accepted
{
  "ok": true,
  "data": {
    "status": "valid"
  }
}

Create a contact and immediately push them to a specific campaign (sequence) in Reply.io.

Install

Add create contact and push to campaign (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-push-contact-to-campaign

When to use this.

The "Create Contact and Push to Campaign" action in Reply.io allows users to efficiently create a new contact and immediately add them to a designated campaign or sequence. This integration is particularly useful for marketing teams looking to streamline their outreach efforts. Key input parameters include "campaignId," which specifies the target campaign for the contact, "email," which captures the contact's email address, and "firstName," which records the contact's first name. Upon execution, the action returns a response status indicating the success or failure of the operation. This action is ideal for use cases such as onboarding new leads, automating marketing workflows, and enhancing customer engagement strategies, making it a valuable tool for any organization focused on effective campaign management.

Try it

Run a sample request.

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

Create Contact and Push to Campaign (Reply.io)

Try it

The ID of the campaign to push the contact

The email address of the contact.

The first name of the contact.

Response is cached — no live API call.

Response

Output schema.

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

FieldType
  • status
    Status
    string

Integrate

Copy-pasteable snippets.

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

cURL · api.texau.app
84ms
POST/v1/reply-push-contact-to-campaign
curl -X POST 'https://v3-api.texau.com/api/v1/reply-push-contact-to-campaign' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"campaign_id":"sample-value","email":"[email protected]","first_name":"Jane"}'
200 Accepted
{
  "ok": true,
  "data": {
    "status": "valid"
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Create Contact and Push to Campaign (Reply.io)→Delete Contact By ID (Reply.io)→Push Existing Contact to Campaign (Reply.io)

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

Step 1TriggerNew row, webhook, or schedule.
Step 2Create Contact and Push to Campaign (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.

Related

More Reply 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__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 Create Contact and Push to Campaign (Reply.io) in 60 seconds.

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

Start free →Read the API docs