TexAu integrates with Reply. Enrich, sync, and automate every action from one API. Bring it into Claude, Cursor, or any MCP client. Built for sales, RevOps, and growth teams who want a programmable layer on top.
Built for Sales, RevOps, and growth teams running outbound..
What you can build
Three workflows worth shipping with Reply.
Enrich every new record before it hits Reply
Run the 32-integration waterfall on inbound, write the verified result back.
Sync TexAu Tables to Reply on a schedule
Bidirectional sync, conflict resolution, custom field mapping.
Trigger Reply actions from Claude or your API
Every action exposed as an MCP tool. Call it from any agent.
The catalog
Every Reply action TexAu supports.
Grouped by verb. Each row links to the full input/output schema and a try-it widget.
Other · 12
Delete Contact By ID (Reply.io)ReplyOutreachPush Existing Contact to Campaign (Reply.io)ReplyOutreachCreate Contact and Push to Campaign (Reply.io)ReplyOutreachDelete Contact by Email (Reply.io)ReplyOutreachGet All Contacts (Reply.io)ReplyOutreachUpdate Contact (Reply.io)ReplyOutreachGet Campaign Details (Reply.io)ReplyOutreachGet Contacts by List Name (Reply.io)ReplyOutreachGet Contact by Email (Reply.io)ReplyOutreachGet Contact by ID (Reply.io)ReplyOutreachCreate Contact (Reply.io)ReplyOutreachGet All Campaigns (Reply.io)ReplyOutreachThe trace
How a Reply workflow runs.
Reply → TexAu enrichment → Reply writeback. One trace, every step observable.
ReplyReplyAuth & setup
Connect Reply in four steps.
- 1
Generate an API key in Reply
Reply settings → API → Create new key.
- 2
Open Studio → Connections → Reply
Paste the key. We store it encrypted at rest.
- 3
We test the connection on save
Bad key? You see the error inline before any workflow runs.
- 4
Run your first action
Pick any action from the catalog above and try it live.
MCP for Reply
Bring Reply into Claude, Cursor, or any MCP client.
Drop this into your config. Every action above becomes a tool the model can call.
{ "mcpServers": { "texau-reply": { "command": "npx", "args": ["-y", "@texau/mcp-server"], "env": { "TEXAU_API_KEY": "...", "TEXAU_PLATFORM": "reply" }, "tools": [ "reply-delete-by-id-person", "reply-push-existing-contact-to-sequence", "reply-push-contact-to-campaign", "reply-delete-contact-by-email", "reply-get-all-people" ] } } }
Compared
Where TexAu wins vs native Reply automation.
Enrichment depth
Native: one provider. TexAu: 32-integration waterfall with attribution.
Branching logic
Native: linear. TexAu: real conditionals, retries, async-safe steps.
AI surface
Native: none. TexAu: every action is also an MCP tool.
Migration
From Zapier or manual scripts to TexAu.
Most Reply teams land on TexAu after they hit the ceiling of Zapier or manual scripts. The pattern is the same: a workflow worked for the first 10 contacts, then it broke at 1,000. Steps timed out. Branching turned into a Frankenstein. Enrichment was always one provider deep, so half the rows came back empty.
TexAu replaces the brittle middle. The 32-integration waterfall fills the rows that Zapier or manual scripts left empty. Async-safe steps mean a slow LinkedIn fetch does not block the whole run. Branching is real branching, not nested filters. And every action you build for Reply is also an MCP tool. Claude can call it, your API can call it, your Studio operator can run it from a Table.
We import existing workflows. We do not ask you to rebuild from scratch. Most teams are running the same automations on TexAu within a week, with deeper enrichment and observable traces from day one.
Connect Reply in Studio →
Free to start. No credit card. Every action above runs in your first session.