List Users (HubSpot)
HubSpot → List Users (HubSpot)
/v1/hubspot-list-users{ "after": "sample-value", "limit": 1 }
{ "ok": true, "data": { "paging_next_after": "sample", "paging_next_link": "sample", "user_id": "rec_4f3a91", "user_email": "[email protected]", "user_primary_team_id": "rec_4f3a91", "user_role_id": "rec_4f3a91", "user_secondary_team_id": "rec_4f3a91", "user_super_admin_flag": true } }
Retrieve a paginated list of HubSpot users, including email, role, team assignments, and super admin status.
Install
Add list users (hubspot) to your MCP client.
Drop this into claude_desktop_config.json (or your client's equivalent) and the tool shows up in any chat.
{ "mcpServers": { "texau": { "command": "npx", "args": ["-y", "@texau/mcp-server"], "env": { "TEXAU_API_KEY": "..." } } } }
Tool name: texau__hubspot-list-users
When to use this.
The "List Users (HubSpot)" action enables users to retrieve a paginated list of HubSpot users, providing essential information such as email addresses, roles, team assignments, and super admin status. Key input parameters include "after," a cursor token for pagination, and "limit," which specifies the maximum number of users to retrieve (up to 100 per page). The output fields include "paging_next_after" and "paging_next_link" for navigation, along with user-specific data such as "user_ids," "user_emails," "user_primary_team_ids," "user_role_ids," "user_secondary_team_ids," and "user_super_admin_flags." This action is particularly useful for CRM applications, allowing organizations to efficiently manage user data, streamline team assignments, and monitor administrative roles within HubSpot.
Try it
Run a sample request.
The response is a deterministic, cached example. No live call, no credits used.
List Users (HubSpot)
Response
Output schema.
Every field returned in `data`. Click rows to expand nested objects.
paging_next_afterPaging Next Afternullablestringpaging_next_linkPaging Next Linknullablestringuser_idUser Idstringuser_emailUser Emailstringuser_primary_team_idUser Primary Team Idnullablestringuser_role_idUser Role Idnullablestringuser_secondary_team_idUser Secondary Team Idnullablearrayuser_super_admin_flagUser Super Admin Flagnullableboolean
Integrate
Copy-pasteable snippets.
Real endpoint: https://v3-api.texau.com/api/v1/hubspot-list-users. Auth: x-api-key.
/v1/hubspot-list-userscurl -X POST 'https://v3-api.texau.com/api/v1/hubspot-list-users' \ -H 'x-api-key: $TEXAU_API_KEY' \ -H 'content-type: application/json' \ -d '{"after":"sample-value","limit":1}'
{ "ok": true, "data": { "paging_next_after": "sample", "paging_next_link": "sample", "user_id": "rec_4f3a91", "user_email": "[email protected]", "user_primary_team_id": "rec_4f3a91", "user_role_id": "rec_4f3a91", "user_secondary_team_id": "rec_4f3a91", "user_super_admin_flag": true } }
Compose
How this fits a workflow.
The next 2 actions most operators chain after this one.
crm
List Contacts (HubSpot)
Retrieves all HubSpot contacts with email, name, phone, company, and custom properties.
Get Contact (HubSpot)
Retrieves a specific HubSpot contact by ID with all standard, demographic, and custom properties.
Create Company (HubSpot)
Creates a new company record in HubSpot with firmographic properties and optional associations.
Output
Results land in a TexAu table.
Sample rows below.
Real result preview coming soon.
| Input | Status | Score |
|---|---|---|
| [email protected] | valid | 96 |
| [email protected] | risky | 54 |
| [email protected] | invalid | 12 |
Workflow
A real example.
Trigger → list users (hubspot) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.
Built for
Who runs this.
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.
| Code | Cause | Fix |
|---|---|---|
| 200 OK | Action ran. Data in `data`. | Read response. |
| 400 Bad Request | Missing or malformed input. | Validate against the input schema. |
| 401 Unauthorized | Missing or invalid `x-api-key`. | Re-issue from /api-platform. |
| 403 Forbidden | Workspace lacks plan tier. | Upgrade or contact sales. |
| 404 Not Found | Action key not recognized. | Verify the slug. |
| 429 Rate Limited | Per-minute or per-day cap hit. | Backoff; reduce concurrency. |
| 500 Server Error | Unexpected TexAu issue. | Retry with backoff. |
| 502 Bad Gateway | Upstream provider 5xx. | Retry; we surface root cause. |
| 504 Timeout | Upstream slower than maxLatency. | Switch to `isAsync` polling. |
Related
More HubSpot actions.
List Contacts (HubSpot)
Retrieves all HubSpot contacts with email, name, phone, company, and custom properties.
Get Contact (HubSpot)
Retrieves a specific HubSpot contact by ID with all standard, demographic, and custom properties.
Create Company (HubSpot)
Creates a new company record in HubSpot with firmographic properties and optional associations.
Search Contacts (HubSpot)
Search for HubSpot CRM contacts by email address or other filters and retrieve their properties.
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__hubspot-...` 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 (HubSpot) in 60 seconds.
Pull your API key, paste the cURL, ship to your CRM.