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
Action → Create
AI-generatedSummary
Create a new action associated with a specific ticket in HaloPSA by providing required ticket ID and note content, with options to specify various additional details about the action such as the performing agent, related contract, arrival and completion dates, and visibility settings.
Inputs
- Ticket ID (required) — The ID of the ticket to create the action for
- Note (required) — The content/note for the action
- Additional Fields — Optional fields to further specify details about the action, including arrival date, completion date, performing agent, contract associations, project ID, pinning and visibility options, and other contextual metadata.
Output shape
An object representing the newly created action record with all supplied attributes and system-generated data as returned by the HaloPSA API after creation.
The output includes the action resource data object created; no pagination applies since a single action is created per execution.
Examples
Example 1: Create an action for a ticket with essential note content.
Provide the ticket ID and the note text describing the action to be created.
Example 2: Create an action with additional metadata specifying agent and scheduling details.
Set the ticket ID, note, and fill additional optional fields like action by agent, action arrival date, and hidden from user flag.