Reply logo

Push Existing Contact to Campaign (Reply.io)

Reply → Push Existing Contact to Campaign (Reply.io)

POST/v1/reply-push-existing-contact-to-sequence
texau__reply-push-existing-contact-to-sequenceintegration
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/reply-push-existing-contact-to-sequence
{
  "campaign_id": "sample-value",
  "email": "[email protected]"
}
200 Accepted
{
  "ok": true,
  "data": {
    "push_prospect_id": "rec_4f3a91"
  }
}

Push an existing contact to a selected campaign

Install

Add push existing contact 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-existing-contact-to-sequence

When to use this.

The "Push Existing Contact to Campaign" action in Reply.io allows users to seamlessly integrate their existing contacts into targeted marketing campaigns. This action requires two key input parameters: the campaignId, which identifies the specific campaign for the contact, and the email address of the existing contact to be pushed. It is important to note that the contact will only be moved if they are not currently enrolled in any active campaign. Upon successful execution, the action returns a unique pushed prospect ID, enabling users to track the contact's status within the campaign. This functionality is particularly useful for marketing teams looking to streamline their outreach efforts and ensure that valuable contacts are effectively engaged in their campaigns. As part of the integration category, this action enhances the efficiency of contact management within marketing workflows.

Try it

Run a sample request.

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

Push Existing Contact to Campaign (Reply.io)

Try it

The ID of the campaign to which the contact should be pushed.

The email address of the existing contact.

Response is cached — no live API call.

Response

Output schema.

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

FieldType
  • push_prospect_id
    Push Prospect Id
    string

Integrate

Copy-pasteable snippets.

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

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

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Push Existing Contact to Campaign (Reply.io)→Delete Contact By ID (Reply.io)→Create Contact and Push 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 → push existing contact 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 2Push Existing Contact 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 Push Existing Contact to Campaign (Reply.io) in 60 seconds.

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

Start free →Read the API docs