Actions67
- User Actions
- Teams Actions
- Custom Fields Actions
- Tickets Actions
- Ticket Status Actions
- Deals Actions
- Webhooks Actions
- Contacts Actions
- Companies Actions
- Bussiness Types Actions
- Tags Actions
- Deal Phases Actions
- Invoices Actions
- Subscriptions Actions
- Products Actions
- Projects Actions
- Tasks Actions
- Files Actions
- Notes Actions
Tickets → Create
AI-generatedOverview
This node operation creates a new ticket in the Teamleader system. It is useful for automating customer support workflows by programmatically generating tickets with specified details such as subject, description, customer information, assignee, and ticket status. For example, it can be used to automatically create support tickets from incoming emails or form submissions.
Use Case Examples
- Automatically create a support ticket when a customer submits a contact form on a website.
- Generate a ticket in Teamleader when an issue is reported via a chatbot.
Properties
| Name | Meaning |
|---|---|
| Subject | The subject of the ticket, describing the main topic or issue. |
| Description | A detailed description of the ticket content or issue. |
| Customer | The ID and type (company or contact) of the customer the ticket is for, specified as a fixed collection with type and ID fields. |
| Assignee | The user the ticket is assigned to, specified as a fixed collection with type (default 'user') and ID fields. |
| Ticket Status ID | The ID of the status to set the ticket to, indicating the current state of the ticket. |
Output
JSON
id- The unique identifier of the created ticket.subject- The subject of the created ticket.description- The description of the created ticket.customer- Information about the customer associated with the ticket.assignee- Information about the user assigned to the ticket.ticket_status_id- The status ID assigned to the ticket.
Dependencies
- Requires an OAuth2 API credential for Teamleader to authenticate requests.
Troubleshooting
- Common issues include missing required fields such as subject, description, customer ID, or ticket status ID, which will cause the API to reject the request.
- Errors may occur if the OAuth2 token is invalid or expired; re-authentication may be necessary.
- If the customer or assignee IDs are incorrect or do not exist in Teamleader, the API will return an error.
Links
- Teamleader API Documentation - Official documentation for the Teamleader API, useful for understanding ticket creation and other operations.