Actions290
- Action Actions
- Agent Actions
- Appointment Actions
- Approval Process Actions
- Approval Process Rule Actions
- Asset Actions
- Attachment Actions
- Automation Actions
- Canned Text Actions
- Category Actions
- Client Actions
- Contract Actions
- Contract Rule Actions
- Contract Schedule Actions
- Contract Schedule Plan Actions
- Custom API Call Actions
- Feed Actions
- Field Info Actions
- Holiday Actions
- Invoice Actions
- Invoice Payment Actions
- Item Actions
- Knowledge Base Actions
- Lookup Actions
- Notification Actions
- Opportunity Actions
- Outcome Actions
- Product Branch Actions
- Product Component Actions
- Project Actions
- Purchase Order Actions
- Quotation Actions
- Raynet Actions
- Raynet Detail Actions
- Recurring Invoice Actions
- Release Actions
- Release Note Group Actions
- Reporting Actions
- Sales Order Actions
- Secure Secret Link Actions
- Security Check Actions
- Site Actions
- Supplier Actions
- Survey Actions
- Tag Actions
- Team Actions
- Ticket Actions
- Ticket Approval Actions
- Ticket Status Actions
- Ticket To-Do Actions
- Ticket Type Actions
- Timesheet Actions
- Timesheet Event Actions
- Top Level Actions
- Transcription Actions
- User Actions
- Webhook Actions
- Webhook Event Actions
User → Get by ID
AI-generatedSummary
Retrieve one HaloPSA user by ID, with optional filters and flags controlling related information in the response.
Inputs
- User ID (required) — Numeric ID of the user to retrieve.
- Options — Optional filters and response flags: client and site IDs or overrides, domain (the only listed choice is Opportunities), opportunity ID, supplier ID, ticket type ID, username, setup filter, and flags to include activity, billing information, details, popups, or user assets.
- Options (JSON) — Dynamic options as a JSON object; values override matching keys in Options. Supports expressions, for example {"client_id": {{ $json.client_id }}}.
Output shape
A single user record
The selected include flags and filters may affect the returned record. The supplied source pack shows only the operation's function signature, so it does not establish the exact response envelope.