Delete Contact by Email (Reply.io)
Reply → Delete Contact by Email (Reply.io)
/v1/reply-delete-contact-by-email{ "email": "[email protected]" }
{ "ok": true, "data": { "status": "valid" } }
Delete a specific contact from Reply.io using their email address.
Install
Add delete contact by email (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.
{ "mcpServers": { "texau": { "command": "npx", "args": ["-y", "@texau/mcp-server"], "env": { "TEXAU_API_KEY": "..." } } } }
Tool name: texau__reply-delete-contact-by-email
When to use this.
The "Delete Contact by Email" action in Reply.io allows users to efficiently remove a specific contact from their CRM system using the contact's email address. This action requires a single input parameter, the "email" (string), which specifies the email address of the contact to be deleted. Upon execution, the action returns a status indicating the success or failure of the deletion process. This functionality is essential for maintaining an organized and up-to-date contact list, making it particularly useful for businesses that need to manage their customer relationships effectively. By leveraging this action, users can streamline their CRM operations, ensuring that outdated or incorrect contact information is promptly removed, thus enhancing overall data integrity.
Try it
Run a sample request.
The response is a deterministic, cached example. No live call, no credits used.
Delete Contact by Email (Reply.io)
Response
Output schema.
Every field returned in `data`. Click rows to expand nested objects.
statusStatusstring
Integrate
Copy-pasteable snippets.
Real endpoint: https://v3-api.texau.com/api/v1/reply-delete-contact-by-email. Auth: x-api-key.
/v1/reply-delete-contact-by-emailcurl -X POST 'https://v3-api.texau.com/api/v1/reply-delete-contact-by-email' \ -H 'x-api-key: $TEXAU_API_KEY' \ -H 'content-type: application/json' \ -d '{"email":"[email protected]"}'
{ "ok": true, "data": { "status": "valid" } }
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.
| Input | Status | Score |
|---|---|---|
| [email protected] | valid | 96 |
| [email protected] | risky | 54 |
| [email protected] | invalid | 12 |
Workflow
A real example.
Trigger → delete contact by email (reply.io) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.
Built for
Who runs this.
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.
| Code | Cause | Fix |
|---|---|---|
| 200 OK | Action ran. Data in `data`. | Read response. |
| 400 Bad Request | Missing or malformed input. | Validate against the input schema. |
| 401 Unauthorized | Missing or invalid `x-api-key`. | Re-issue from /api-platform. |
| 403 Forbidden | Workspace lacks plan tier. | Upgrade or contact sales. |
| 404 Not Found | Action key not recognized. | Verify the slug. |
| 429 Rate Limited | Per-minute or per-day cap hit. | Backoff; reduce concurrency. |
| 500 Server Error | Unexpected TexAu issue. | Retry with backoff. |
| 502 Bad Gateway | Upstream provider 5xx. | Retry; we surface root cause. |
| 504 Timeout | Upstream slower than maxLatency. | Switch to `isAsync` polling. |
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 Delete Contact by Email (Reply.io) in 60 seconds.
Pull your API key, paste the cURL, ship to your CRM.