Actions125
- Ticket Actions
- Ticket Note Actions
- Ticket Attachment Actions
- Company Actions
- Company Note Actions
- Company Attachment Actions
- Contact Actions
- Resource (Employee) Actions
- Contract Actions
- Contract Note Actions
- Project Actions
- Project Note Actions
- Task Actions
- Task Note Actions
- Time Entry Actions
- Configuration Item Actions
- Configuration Item Note Actions
- Product Actions
- Opportunity Actions
- Quote Actions
- Quote Item Actions
- Service Call Actions
- Invoice Actions
- Subscription Actions
- Inventory Item Actions
- Purchase Order Actions
- Purchase Order Item Actions
Ticket → Create Ticket
AI-generatedSummary
Create a new ticket in Autotask with specified details such as title, company, status, priority, queue, and source. Optional fields include issue types, description, assigned resource, contact, due date, and additional metadata.
Inputs
- Title (required) — Short summary of the ticket.
- Company (required) — The company this ticket belongs to, chosen from a dynamically loaded list of active companies.
- Status (required) — Current status of the ticket, selectable from active ticket statuses.
- Priority (required) — Priority level of the ticket, selectable from available priority options.
- Queue (required) — Queue where the ticket will be assigned, selectable from available ticket queues.
- Source (required) — Source of the ticket, selectable from available ticket sources.
- Issue Type — Optional issue type category for the ticket.
- Sub Issue Type — Optional subcategory of the issue type; Autotask validates this against the selected issue type.
- Description — Detailed description of the ticket's issue.
- Assigned Resource — Employee resource assigned to the ticket.
- Contact — Primary contact person at the associated company.
- Due Date — Deadline for the ticket resolution, specified as date and time.
- Additional Fields — Optional extra fields such as ticket category, contract, estimated hours, external reference number, and resolution note.
- Extra Fields (JSON) — A JSON object to provide any additional or override fields not exposed through the UI parameters.
- Header Overrides — Optional HTTP header overrides, including impersonation resource ID for API requests.
Output shape
a single record representing the created ticket, with its properties as returned by the Autotask API.
The output is a single created ticket object. All required fields must be provided, and optional fields can be omitted. Any extra JSON fields in 'Extra Fields (JSON)' override the standard parameters. Errors in creation will cause node failure unless 'Continue On Fail' is enabled.
Examples
Example 1: Create a ticket with mandatory fields and an optional description
Set Title, Company, Status, Priority, Queue, and Source parameters; optionally provide a Description.
