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 → Create
AI-generatedSummary
Create a HaloPSA user for a selected client and site, with optional contact and account settings.
Inputs
- Name (required) — Full name of the new user.
- Email Address (required) — Email address for the new user.
- Client Name or ID (required) — Client the user belongs to; select a client or provide its ID, including through an expression.
- Site Name or ID (required) — Site the user belongs to; select a site or provide its ID. The site choices depend on the selected client.
- Additional Fields — Optional user details: colour, first name, surname, initials, phone numbers, WhatsApp number, site phone number, linked agent ID, priority ID, telephone preference, and flags for inactive, important contact (primary or secondary), service account, automated billing exclusion, and suppressing emails.
Output shape
A single created user record
The supplied source pack shows only the operation's function signature, so the exact response fields are not visible.