Actions60
- User Actions
- Teams Actions
- Custom Fields Actions
- Tickets 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
Overview
This node integrates with the Teamleader API to manage support tickets. Specifically, the Tickets - Create operation allows users to create new support tickets within their Teamleader account. This is useful for automating customer support workflows, such as logging issues reported by customers or tracking internal tasks related to customer requests.
Typical use cases include:
- Automatically creating a ticket when a customer submits a form on a website.
- Logging issues from other systems into Teamleader for centralized tracking.
- Assigning tickets to specific users or teams based on predefined rules.
For example, you could set up an automation that creates a ticket with a subject and description, associates it with a specific customer (company or contact), assigns it to a user, and sets its initial status.
Properties
| Name | Meaning |
|---|---|
| Subject | The subject/title of the ticket. |
| Description | A detailed description of the issue or request in the ticket. |
| Customer | The customer the ticket is for. Choose between a Company or Contact type and provide its ID. |
| Assignee | (Optional) The user the ticket is assigned to. Specify type (always "user") and user ID. |
| Ticket Status ID | The ID of the status to assign to the ticket upon creation (e.g., "Open", "Pending"). |
Output
The node outputs an array of JSON objects representing the created ticket(s). Each object contains the data returned by the Teamleader API for the newly created ticket, including all relevant ticket details such as ID, subject, description, customer info, assignee, status, timestamps, and any other metadata provided by the API.
No binary data output is involved.
Dependencies
- Requires an OAuth2 API credential configured in n8n to authenticate with the Teamleader API.
- The node makes HTTP POST requests to the Teamleader API endpoint
https://api.focus.teamleader.euusing the/tickets.createoperation. - Proper permissions in the Teamleader account are needed to create tickets.
Troubleshooting
- No data returned but request was successful: This message indicates the API call succeeded but returned no ticket data. Verify that all required fields (subject, description, customer, ticket status) are correctly set.
- No data got returned: If the API response lacks expected data, check if the API credentials are valid and have sufficient permissions.
- API errors: Errors from the Teamleader API will be thrown as node errors. Common causes include invalid IDs for customer or status, missing required fields, or authentication failures.
- Ensure the customer ID corresponds to an existing company or contact in Teamleader.
- The ticket status ID must be valid and active in your Teamleader setup.
- If assigning a user, verify the user ID exists and has permission to be assigned tickets.
Links and References
- Teamleader API Documentation
- Teamleader Tickets API Reference (for detailed field descriptions and status IDs)