Search Users
Search_Users returns GovTribe workspace user records by matching name or email text and provides canonical user IDs for downstream tool calls.
When To Use
Typical questions this tool answers well:
Which workspace user matches this exact name?
Which workspace user owns this email address?
What user IDs should I pass to
owner_ids,creator_ids, or task owner fields in other tools?Which known user IDs should I include or exclude before running downstream updates?
How many users match a lookup without fetching full rows?
Required Reading
Search_Query_Guide: Required before setting free-text query strings when search_mode is used.
Search_Mode_Guide: Required before choosing keyword vs semantic retrieval.
Input Contract
query: Free-text query string. See Required Reading: Search_Query_Guide.type:stringrequired:nodefault:n/a
page: 1-based page index.type:null|numberrequired:nodefault:1
per_page: Rows per page.type:null|numberrequired:nodefault:10
search_mode: Query interpretation mode. See Required Reading: Search_Mode_Guide.type:stringrequired:nodefault:keywordoptions:keyword,semantic
user_ids: Include or exclude results by GovTribe IDs.type:array<string>required:nodefault:n/a
user_ids_operator: Choose whether to include or exclude values for GovTribe IDs.type:null|stringrequired:nodefault:inoptions:in,not_in
fields_to_return: Optional field list for row payloads. If omitted andper_page > 0, rows default togovtribe_id. Forper_page: 0aggregation/meta calls, this field may be omitted. Specifyfields_to_returnwhenever the user asks for fields beyondgovtribe_id, and prefer omitting it in pure aggregation workflows.type:array<string>required:nodefault:n/aoptions:govtribe_id,govtribe_type,name,email,phone,updated_at,created_at
Output Contract
Top-level keys:
current_page: Current page number whenper_page > 0.data: Array of result rows whenper_page > 0.from: First row position in the current page.last_page: Last page number for current filters.path: GovTribe search URL for this result set.per_page: Applied page size.to: Last row position in the current page.total: Total matched row count for current query filters.contains: Dataset label for the returned result set.search_results_id_can_generate_saved_search: Saved-search eligibility flag.search_results_id: Server-side search result identifier.view_search_results_url: URL to open this exact result set.per_page: 0behavior: response omits row/pagination keys and returnspath,total,contains,search_results_id_can_generate_saved_search,search_results_id, andview_search_results_url.
Row keys:
govtribe_idgovtribe_typenameemailphoneupdated_atcreated_at
Relationship retrieval map:
none: This resource has no relationship fields.
Usage Patterns
Pattern A: Resolve a user by exact display name. Tool: Search_Users
Pattern B: Resolve a user by exact email address. Tool: Search_Users
Pattern C: Exclude known users while running a broad lookup. Tool: Search_Users
Pattern D: Count matches and capture reusable search-result metadata without row retrieval. Tool: Search_Users
Pattern E: Resolve owner IDs for downstream pipeline/task filtering. Tool: Search_Users
Last updated
Was this helpful?
