Actions389
- Ticket History Actions
- Ticket Note Actions
- Ticket Note Webhook Actions
- Ticket Webhook Actions
- Time Entry Actions
- Resource Actions
- Resource Role Actions
- Role Actions
- Search Filter Actions
- Service Actions
- Service Call Actions
- Skill Actions
- Survey Actions
- Survey Results Actions
- Ticket Actions
- Invoice Actions
- Notification History Actions
- Opportunity Actions
- Product Actions
- Product Vendor Actions
- Project Actions
- Project Charge Actions
- Project Note Actions
- Project Phase Actions
- Project Task Actions
- Contract Retainer Actions
- Contract Service Actions
- Contract Service Adjustment Actions
- Contract Service Bundle Adjustment Actions
- Contract Service Bundle Actions
- Contract Service Bundle Unit Actions
- Contract Ticket Purchase Actions
- Contract Service Unit Actions
- Domain Registrar Actions
- Holiday Actions
- Holiday Set Actions
- Contract Exclusion Billing Code Actions
- Contract Exclusion Role Actions
- Contract Exclusion Sets Actions
- Contract Exclusion Set Excluded Role Actions
- Contract Exclusion Set Excluded Work Type Actions
- Contract Milestone Actions
- Contract Note Actions
- Contract Rate Actions
- Contract Role Costs Actions
- Contact Actions
- Contact Webhook Actions
- Contact Groups Actions
- Contact Group Contacts Actions
- Contract Actions
- Contract Block Actions
- Contract Block Hour Factor Actions
- Contract Billing Rule Actions
- Contract Charge Actions
- Configuration Item Category Actions
- Configuration Item Category UDF Association Actions
- Configuration Item DNS Record Actions
- Configuration Item Note Actions
- Configuration Item Related Item Actions
- Configuration Item SSL Subject Alternative Name Actions
- Configuration Item Type Actions
- Configuration Item Webhook Actions
- Billing Code Actions
- Company Actions
- Company Alert Actions
- Company Location Actions
- Company Note Actions
- Company Webhook Actions
- Configuration Item Actions
- Configuration Item Billing Product Association Actions
Ticket → Create
AI-generatedOverview
This node integrates with the Autotask REST API to perform operations on various resources. Specifically, for the 'Ticket' resource with the 'Create' operation, it allows users to create new tickets in Autotask by mapping input fields to the ticket properties. This is useful for automating ticket creation workflows, such as generating support tickets from form submissions or monitoring systems.
Properties
| Name | Meaning |
|---|---|
| Fields | Defines the mapping of input data fields to the Autotask ticket fields for creation. Users specify which ticket fields to populate and with what values. |
Output
JSON
id- The unique identifier of the created ticket.number- The ticket number assigned by Autotask.status- The current status of the created ticket.priority- The priority level assigned to the ticket.summary- A brief summary or title of the ticket.createdDate- The date and time when the ticket was created.assignedResourceId- Identifier of the resource (user or team) assigned to the ticket.
Dependencies
- Requires an Autotask API key credential for authentication to the Autotask REST API.
Troubleshooting
- Error: 'Resource ticket is not supported' - Ensure the resource parameter is set to 'ticket'.
- Error: Missing required fields in the mapping - Verify that all mandatory ticket fields are mapped in the 'Fields' property.
- Authentication errors - Confirm that the Autotask API credentials are correctly configured and valid.
- API rate limits - If requests fail due to rate limiting, consider adding delays or retries.
Links
- Autotask REST API Documentation - Official documentation for Autotask API endpoints and data models.