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