Apollo on TexAu
Drive Apollo 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 Apollo actions
Quick links into the 4-action catalog. Each action page has the full input/output schema and a try-it widget.
Enrich Company (Apollo)
apollo-enrich-organization-by-domainRetrieve enriched company/organization details from Apollo by providing a website domain. Returns firmographic data such as company name, location, size, funding, technologies used, and related account information.
Find Email using Linkedin Url (Apollo)
apollo-enrich-person-using-linkedinFind Email using Linkedin Url (Apollo)
Find Email using Name and Domain(Apollo)
apollo-enrich-personFind Email using Name and Domain(Apollo)
Find Mobile Number using Name and Domain(Apollo)
apollo-find-numberFind Mobile Number using Name and Domain(Apollo)
What teams build
Common Apollo workflows on TexAu
Enrich on the way in
Trigger on a new Apollo 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 Apollo into Claude, Cursor, or any MCP client with one config block.
Related other apps
Other Other integrations
FAQ
Apollo on TexAu — common questions
How many Apollo actions does TexAu support?
TexAu supports 4 public Apollo actions. Every action is callable as REST and as an MCP tool.
Can I call Apollo from Claude or Cursor?
Yes. Every Apollo action on TexAu is exposed as an MCP tool, so Claude, Cursor, and any MCP client can invoke it directly.
Is Apollo sync bidirectional on TexAu?
TexAu can both pull from and push to Apollo via REST. For full bidirectional CRM-style sync, see the CRM apps in the directory.