Get All Campaigns (Reply.io)
Reply → Get All Campaigns (Reply.io)
/v1/reply-get-all-campaigns{}{ "ok": true, "data": { "campaign_id": "rec_4f3a91", "campaign_name": "sample", "campaign_status": "valid", "campaign_created_at": "sample", "campaign_is_archived": true, "campaign_email_account": "[email protected]" } }
Retrieves a list of all campaigns from Reply.io including creation time, status, and archive state.
Install
Add get all campaigns (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-get-all-campaigns
When to use this.
The "Get all Campaigns" action for Reply.io enables users to efficiently retrieve a comprehensive list of campaigns from the Reply.io platform. This action does not require any input parameters, making it straightforward to implement. The output includes essential details such as campaign_id (id), campaign_name (text), campaign_status (text), campaign_created_at (date), campaign_is_archived (boolean), and campaign_email_account (text). This functionality is particularly useful for marketing teams and sales professionals looking to analyze campaign performance, track statuses, and manage archived campaigns. By integrating this action into their workflow, users can enhance their campaign management processes and gain valuable insights into their marketing strategies.
Response
Output schema.
Every field returned in `data`. Click rows to expand nested objects.
campaign_idCampaign Idnumbercampaign_nameCampaign Namestringcampaign_statusCampaign Statusstringcampaign_created_atCampaign Created Atnullablestringcampaign_is_archivedCampaign Is Archivednullablebooleancampaign_email_accountCampaign Email Accountnullablestring
Integrate
Copy-pasteable snippets.
Real endpoint: https://v3-api.texau.com/api/v1/reply-get-all-campaigns. Auth: x-api-key.
/v1/reply-get-all-campaignscurl -X POST 'https://v3-api.texau.com/api/v1/reply-get-all-campaigns' \
-H 'x-api-key: $TEXAU_API_KEY' \
-H 'content-type: application/json' \
-d '{}'{ "ok": true, "data": { "campaign_id": "rec_4f3a91", "campaign_name": "sample", "campaign_status": "valid", "campaign_created_at": "sample", "campaign_is_archived": true, "campaign_email_account": "[email protected]" } }
Compose
How this fits a workflow.
The next 2 actions most operators chain after this one.
integration
Push Existing Contact to Campaign (Reply.io)
Push an existing contact to a selected campaign. Note: The contact will only be moved if they are not currently in any active campaign.
integration
Create Contact and Push to Campaign (Reply.io)
Create a contact and immediately push them to a specific campaign (sequence) in Reply.io.
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 → get all campaigns (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. |
Related
More Reply actions.
integration
Push Existing Contact to Campaign (Reply.io)
Push an existing contact to a selected campaign. Note: The contact will only be moved if they are not currently in any active campaign.
integration
Create Contact and Push to Campaign (Reply.io)
Create a contact and immediately push them to a specific campaign (sequence) in Reply.io.
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 Get All Campaigns (Reply.io) in 60 seconds.
Pull your API key, paste the cURL, ship to your CRM.