Reply on TexAu
Drive Reply from your code, your CRM, or directly from Claude and Cursor. Every action is exposed as REST and as an MCP tool — no glue code, no Zapier middleman.
Top actions
Most-used Reply actions
Quick links into the 12-action catalog. Each action page has the full input/output schema and a try-it widget.
Create Contact (Reply.io)
reply-create-contactCreate a new contact in Reply.io or update an existing one if the email exists.
Create Contact and Push to Campaign (Reply.io)
reply-push-contact-to-campaignCreate a contact and immediately push them to a specific campaign (sequence) in Reply.io.
Delete Contact By ID (Reply.io)
reply-delete-by-id-personDeletes a contact from Reply.io using their unique Person ID.
Delete Contact by Email (Reply.io)
reply-delete-contact-by-emailDelete a specific contact from Reply.io using their email address.
Get All Campaigns (Reply.io)
reply-get-all-campaignsRetrieves a list of all campaigns from Reply.io including creation time, status, and archive state.
What teams build
Common Reply workflows on TexAu
Enrich on the way in
Trigger on a new Reply record, run the 32-integration waterfall, write verified fields back.
Sync to a TexAu Table
Pull on a schedule, enrich in a Table, push the deltas back. Custom field mapping, conflict resolution, observable trace.
Call from Claude
Every action above is also an MCP tool. Wire Reply into Claude, Cursor, or any MCP client with one config block.
Related other apps
Other Other integrations
FAQ
Reply on TexAu — common questions
How many Reply actions does TexAu support?
TexAu supports 12 public Reply actions. Every action is callable as REST and as an MCP tool.
Can I call Reply from Claude or Cursor?
Yes. Every Reply action on TexAu is exposed as an MCP tool, so Claude, Cursor, and any MCP client can invoke it directly.
Is Reply sync bidirectional on TexAu?
TexAu can both pull from and push to Reply via REST. For full bidirectional CRM-style sync, see the CRM apps in the directory.