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
Agent → Create
AI-generatedSummary
Create a HaloPSA agent using a required email address and name, with optional settings for status, department, names, admin access, login, phone number, and team.
Inputs
- Email Address (required) — Email address for the new agent.
- Name (required) — Name for the new agent.
- Active — Controls whether the agent is disabled; false means active and true means disabled.
- Department Name or ID — Department to assign to the agent. Choose a department or provide its ID.
- First Name — Agent's first name.
- Is Admin — Whether the agent has admin privileges.
- Last Name — Agent's surname.
- Login Name — Login name for the agent.
- Phone Number — Agent's phone or SMS number.
- Team Name or ID — Team to assign to the agent. Choose a team or provide its ID.
Output shape
Not established by the provided source view.
The operation's execute implementation is shown only as a function signature, so the request payload and returned data shape cannot be confirmed. The listed inputs are declared by the operation properties.