| name | sales-texau |
| description | TexAu platform help — GTM automation and data platform: cloud/desktop LinkedIn and web automation ('automations'/recipes, automation hours), waterfall enrichment (65+ endpoints), people and lead search, async email finding and verification, web scraping, plus a REST API (base v3-api.texau.com, x-api-key header) and an MCP server (mcp.texau.com/mcp) for Claude and Cursor. Use when a TexAu LinkedIn automation gets your account restricted or banned, automations stall or hit hour limits that don't roll over, enrichment returns low fill rates or no emails, an async email-finding job returns nothing inline, you're wiring TexAu into a CRM or n8n via the API or webhooks, choosing between Cloud, Desktop, and the credit-based API, or budgeting pay-on-match credits. Do NOT use for cross-tool prospect-list strategy (use /sales-prospect-list) or choosing an enrichment provider across tools (use /sales-enrich). |
| argument-hint | [describe what you need help with in TexAu] |
| license | MIT |
| version | 1.0.0 |
| tags | ["sales","prospecting-enrichment","platform"] |
| github | https://github.com/texauhq |
TexAu Platform Help
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated platform knowledge.
Ask only what's needed to route (skip if the prompt already says):
- Which TexAu are you on?
- A) Cloud / Desktop automations (the classic recipe + automation-hours product — LinkedIn, Sales Nav, Twitter, web scraping)
- B) The V3 GTM data platform (table interface, waterfall enrichment, AI Column)
- C) The REST API / MCP server (programmatic, credit-based)
- What's the goal? Build a list · enrich/find emails · scrape a site or directory · wire into a CRM/n8n · pick a plan · debug an account-safety/ban issue.
- Hitting an error? Account restricted · automation stuck · empty enrichment result · async job returns nothing · webhook not firing.
Skip-ahead rule: if the user's prompt already contains enough context, go straight to Step 2.
Step 2 — Route or answer directly
| If the user wants… | Route to |
|---|
| Cross-tool prospect-list strategy (which tool, ICP filters) | /sales-prospect-list {question} |
| Enrichment-provider strategy / waterfall design across tools | /sales-enrich {question} |
| Interpreting job-change / hiring signals across tools | /sales-intent {question} |
| Designing the outbound sequence after the list is built | /sales-cadence {question} |
| Connecting TexAu to a CRM / Zapier / Make generically | /sales-integration {question} |
When routing, give the exact command, e.g. "This is a cross-tool enrichment question — run: /sales-enrich {original question}". Otherwise answer here using Step 3.
Step 3 — TexAu platform reference
Read references/platform-guide.md for the full reference — capabilities and automation surface, pricing/credits, data model, the async email-job flow, and integration recipes. For raw endpoints, methods, and field-level request shapes, read references/texau-api-reference.md.
Answer using only the relevant section. Don't dump the whole guide.
Step 4 — Actionable guidance
You no longer need the guide — focus on the user's situation.
