Pipedrive logo

Pipedrive on TexAu

Other30 actionsMCP-readyREST + Webhooks

Drive Pipedrive 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.

What teams build

Common Pipedrive workflows on TexAu

Enrich on the way in

Trigger on a new Pipedrive 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 Pipedrive into Claude, Cursor, or any MCP client with one config block.

Related other apps

Other Other integrations

FAQ

Pipedrive on TexAu — common questions

  • How many Pipedrive actions does TexAu support?

    TexAu supports 30 public Pipedrive actions. Every action is callable as REST and as an MCP tool.

  • Can I call Pipedrive from Claude or Cursor?

    Yes. Every Pipedrive action on TexAu is exposed as an MCP tool, so Claude, Cursor, and any MCP client can invoke it directly.

  • Is Pipedrive sync bidirectional on TexAu?

    TexAu can both pull from and push to Pipedrive via REST. For full bidirectional CRM-style sync, see the CRM apps in the directory.