TexAu makes Pipedrive a real outbound engine. Automate every action from one API: person, organization, and deal sync, custom field writes, activity logging. Built for SDR teams who hit the ceiling of native Pipedrive automations.
Built for SDR teams and small agencies.
What you can build
Three workflows worth shipping with Pipedrive.
Build a verified outbound list every Monday
Pull from Sales Navigator, enrich, push fresh persons + deals into Pipedrive.
Auto-log every reply on the deal timeline
When a Smartlead reply lands, write an activity to the matching Pipedrive deal.
Score deals with intent data
Pull intent signals weekly, write to a custom field, sort the pipeline.
The catalog
Every Pipedrive action TexAu supports.
Grouped by verb. Each row links to the full input/output schema and a try-it widget.
Other · 30
The trace
How a Pipedrive workflow runs.
Pipedrive → TexAu enrichment → Pipedrive writeback. One trace, every step observable.
CRM ↔ Table ↔ CRM
Bidirectional sync between Pipedrive and TexAu Tables.
Pull a list. Enrich. Write back. Custom field mapping, conflict resolution, deal-stage updates, all handled.
Auth & setup
Connect Pipedrive in four steps.
- 1
Open the Pipedrive app in TexAu
Studio → Connections → Pipedrive.
- 2
Click Connect, we redirect you to Pipedrive
OAuth 2.0 consent screen. You pick the scopes.
- 3
Authorize TexAu
Pipedrive hands us a refresh token. We never see your password.
- 4
Run your first action
Pick any action from the catalog above and try it live.
MCP for Pipedrive
Bring Pipedrive into Claude, Cursor, or any MCP client.
Drop this into your config. Every action above becomes a tool the model can call.
{ "mcpServers": { "texau-pipedrive": { "command": "npx", "args": ["-y", "@texau/mcp-server"], "env": { "TEXAU_API_KEY": "...", "TEXAU_PLATFORM": "pipedrive" }, "tools": [ "pipedrive-get-deals-by-person", "pipedrive-delete-lead", "pipedrive-search-deals", "pipedrive-search-organizations", "pipedrive-create-deal" ] } } }
Compared
Where TexAu wins vs native Pipedrive automation.
Enrichment depth
Native: one provider. TexAu: 32-integration waterfall with attribution.
Branching logic
Native: linear. TexAu: real conditionals, retries, async-safe steps.
AI surface
Native: none. TexAu: every action is also an MCP tool.
Migration
From native Pipedrive automations to TexAu.
Most Pipedrive teams land on TexAu after they hit the ceiling of native Pipedrive automations. The pattern is the same: a workflow worked for the first 10 contacts, then it broke at 1,000. Steps timed out. Branching turned into a Frankenstein. Enrichment was always one provider deep, so half the rows came back empty.
TexAu replaces the brittle middle. The 32-integration waterfall fills the rows that native Pipedrive automations left empty. Async-safe steps mean a slow LinkedIn fetch does not block the whole run. Branching is real branching, not nested filters. And every action you build for Pipedrive is also an MCP tool. Claude can call it, your API can call it, your Studio operator can run it from a Table.
We import existing workflows. We do not ask you to rebuild from scratch. Most teams are running the same automations on TexAu within a week, with deeper enrichment and observable traces from day one.
Connect Pipedrive in Studio →
Free to start. No credit card. Every action above runs in your first session.