Pipedrive logo

List Users (Pipedrive)

PipedriveList Users (Pipedrive)

POST/v1/pipedrive-list-users
texau__pipedrive-list-userscrm
cURL · api.texau.app
84ms
POST/v1/pipedrive-list-users
{}
200 Accepted
{
  "ok": true,
  "data": {
    "success": true,
    "company_id": "rec_4f3a91",
    "user_id": "rec_4f3a91",
    "user_name": "sample",
    "user_email": "[email protected]",
    "user_mobile_number": "sample",
    "user_active_flag": true,
    "user_is_admin_numeric": 1,
    "user_is_deleted": true,
    "user_is_you": true,
    "user_role_id": "rec_4f3a91",
    "user_default_currency": "sample",
    "user_last_login": "sample",
    "user_created_at": "sample",
    "user_modified_at": "sample",
    "user_locale": "sample",
    "user_timezone_name": "sample",
    "user_timezone_offset": "sample",
    "user_language_id": "rec_4f3a91",
    "user_has_created_company": true,
    "user_icon_url": "https://acme.com",
    "user_access_apps": "sample",
    "user_access_is_admin": "sample",
    "user_access_permission_set_ids": "sample"
  }
}

Retrieve a list of users from a Pipedrive account, including IDs, names, emails, roles, and access permissions.

Install

Add list users (pipedrive) to your MCP client.

Drop this into claude_desktop_config.json (or your client's equivalent) and the tool shows up in any chat.

claude_desktop_config.json
{
  "mcpServers": {
    "texau": {
      "command": "npx",
      "args": ["-y", "@texau/mcp-server"],
      "env": { "TEXAU_API_KEY": "..." }
    }
  }
}

Tool name: texau__pipedrive-list-users

When to use this.

The "List Users (Pipedrive)" action allows users to retrieve a comprehensive list of all users associated with a Pipedrive account. This action requires no input parameters, making it straightforward to use. The output includes essential user information such as user IDs, names, emails, roles, and access permissions, along with additional details like last login dates and timezone settings. Key output fields include success status, user active flags, and user access permissions, all represented by various semantic types such as id, fullName, email, and text. This action is particularly useful for CRM administrators and team leaders who need to manage user roles, monitor user activity, and ensure proper access permissions within their Pipedrive environment. By leveraging this action, organizations can enhance user management and streamline their CRM operations.

Response

Output schema.

Every field returned in `data`. Click rows to expand nested objects.

FieldType
  • success
    Success
    nullableboolean
  • company_id
    Company Id
    nullablenumber
  • user_id
    User Id
    number
  • user_name
    User Name
    string
  • user_email
    User Email
    string
  • user_mobile_number
    User Mobile Number
    nullablestring
  • user_active_flag
    User Active Flag
    nullableboolean
  • user_is_admin_numeric
    User Is Admin Numeric
    nullablenumber
  • user_is_deleted
    User Is Deleted
    nullableboolean
  • user_is_you
    User Is You
    nullableboolean
  • user_role_id
    User Role Id
    nullablenumber
  • user_default_currency
    User Default Currency
    nullablestring
  • user_last_login
    User Last Login
    nullablestring
  • user_created_at
    User Created At
    nullablestring
  • user_modified_at
    User Modified At
    nullablestring
  • user_locale
    User Locale
    nullablestring
  • user_timezone_name
    User Timezone Name
    nullablestring
  • user_timezone_offset
    User Timezone Offset
    nullablestring
  • user_language_id
    User Language Id
    nullablenumber
  • user_has_created_company
    User Has Created Company
    nullableboolean
  • user_icon_url
    User Icon Url
    nullablestring
  • user_access_apps
    User Access Apps
    nullablearray
  • user_access_is_admin
    User Access Is Admin
    nullablearray
  • user_access_permission_set_ids
    User Access Permission Set Ids
    nullablearray

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/pipedrive-list-users. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/pipedrive-list-users
curl -X POST 'https://v3-api.texau.com/api/v1/pipedrive-list-users' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{}'
200 Accepted
{
  "ok": true,
  "data": {
    "success": true,
    "company_id": "rec_4f3a91",
    "user_id": "rec_4f3a91",
    "user_name": "sample",
    "user_email": "[email protected]",
    "user_mobile_number": "sample",
    "user_active_flag": true,
    "user_is_admin_numeric": 1,
    "user_is_deleted": true,
    "user_is_you": true,
    "user_role_id": "rec_4f3a91",
    "user_default_currency": "sample",
    "user_last_login": "sample",
    "user_created_at": "sample",
    "user_modified_at": "sample",
    "user_locale": "sample",
    "user_timezone_name": "sample",
    "user_timezone_offset": "sample",
    "user_language_id": "rec_4f3a91",
    "user_has_created_company": true,
    "user_icon_url": "https://acme.com",
    "user_access_apps": "sample",
    "user_access_is_admin": "sample",
    "user_access_permission_set_ids": "sample"
  }
}

Output

Results land in a TexAu table.

Sample rows below.

Real result preview coming soon.

InputStatusScore
[email protected]valid96
[email protected]risky54
[email protected]invalid12

Workflow

A real example.

Trigger → list users (pipedrive) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

Step 1TriggerNew row, webhook, or schedule.
Step 2List Users (Pipedrive)Pipedrive action runs.
Step 3EnrichWaterfall fills missing fields.
Step 4Push to CRMHubSpot / Salesforce / Pipedrive.

Built for

Who runs this.

GTM EngineerRevOpsAgency

Reliability

Rate limits & reliability.

  • Per-minute limitNo public cap
  • Per-day limitPlan-defined
  • RetriesAutomatic w/ backoff
  • ModeSync

Errors

HTTP status codes.

What each response means and what to do about it.

CodeCauseFix
200 OKAction ran. Data in `data`.Read response.
400 Bad RequestMissing or malformed input.Validate against the input schema.
401 UnauthorizedMissing or invalid `x-api-key`.Re-issue from /api-platform.
403 ForbiddenWorkspace lacks plan tier.Upgrade or contact sales.
404 Not FoundAction key not recognized.Verify the slug.
429 Rate LimitedPer-minute or per-day cap hit.Backoff; reduce concurrency.
500 Server ErrorUnexpected TexAu issue.Retry with backoff.
502 Bad GatewayUpstream provider 5xx.Retry; we surface root cause.
504 TimeoutUpstream slower than maxLatency.Switch to `isAsync` polling.

Pricing

What it costs to run.

Light tier

Pricing tier on /pricing. Per-action credit cost is private.

FAQ.

  • Is this real-time?

    Yes. Synchronous actions return in ~1–4 s. Long-running work uses async polling (see status 504 → switch to async).

  • Do I get charged on failure?

    No. Verified failures cost zero credits. Provider miss / 5xx / timeout cascade to the next provider in the waterfall when applicable.

  • Does it work with Claude / Cursor via MCP?

    Yes. Add the texau MCP server to your client config, then call `texau__pipedrive-...` directly.

  • What CRMs can I push results to?

    HubSpot, Salesforce, Pipedrive, Zoho, and GoHighLevel are bidirectional. Smartlead, Instantly, Lemlist, HeyReach, Apollo Sequences, and Reply.io for outbound.

Run List Users (Pipedrive) in 60 seconds.

Pull your API key, paste the cURL, ship to your CRM.