Prospeo on TexAu
Drive Prospeo 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 Prospeo actions
Quick links into the 4-action catalog. Each action page has the full input/output schema and a try-it widget.
Find Email Using Full Name and Company Website (Prospeo)
prospeo-find-emailFinds a professional email address using a person's full name and company website via Prospeo.
Find Email by LinkedIn URL (Prospeo)
prospeo-find-email-using-linkedin-urlFinds a professional email address from a LinkedIn profile URL via Prospeo.
Find Mobile Number Using Full Name and Company Website (Prospeo)
prospeo-find-mobile-numberFinds a mobile phone number using a person's full name and company website via Prospeo.
Find Mobile Number by LinkedIn URL (Prospeo)
prospeo-find-phoneFinds a mobile phone number from a LinkedIn profile URL via Prospeo.
What teams build
Common Prospeo workflows on TexAu
Enrich on the way in
Trigger on a new Prospeo 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 Prospeo into Claude, Cursor, or any MCP client with one config block.
Related other apps
Other Other integrations
FAQ
Prospeo on TexAu — common questions
How many Prospeo actions does TexAu support?
TexAu supports 4 public Prospeo actions. Every action is callable as REST and as an MCP tool.
Can I call Prospeo from Claude or Cursor?
Yes. Every Prospeo action on TexAu is exposed as an MCP tool, so Claude, Cursor, and any MCP client can invoke it directly.
Is Prospeo sync bidirectional on TexAu?
TexAu can both pull from and push to Prospeo via REST. For full bidirectional CRM-style sync, see the CRM apps in the directory.