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
The "Update Ticket" operation in this node allows users to modify existing support tickets within the Teamleader system via its API. This is useful for scenarios where ticket details such as subject, description, assignee, or status need to be changed after creation. For example, a customer support agent might update the ticket's subject to better reflect the issue or assign the ticket to another team member for resolution.
Properties
| Name | Meaning |
|---|---|
| Subject | The subject/title of the ticket. |
| Description | Detailed description of the ticket's issue or content. |
| Assignee | The user assigned to handle the ticket. Consists of a type (usually "user") and an ID. |
| Ticket Status ID | The identifier of the status to set the ticket to (e.g., open, closed, pending). |
| ID | The unique identifier of the ticket to update. |
Output
The node outputs JSON data representing the updated ticket information returned by the Teamleader API. The structure typically includes all relevant fields of the ticket after the update, such as its ID, subject, description, assignee details, status, timestamps, and any other metadata provided by the API.
No binary data output is involved in this operation.
Dependencies
- Requires an OAuth2 API credential configured for Teamleader with appropriate permissions to update tickets.
- The node communicates with the Teamleader API endpoint at
https://api.focus.teamleader.euusing POST requests. - Proper API authentication token must be available in n8n credentials for successful requests.
Troubleshooting
Common Issues:
- Missing or invalid ticket ID will cause the update to fail.
- Providing empty required fields like subject or description may result in errors.
- Incorrect or unauthorized API credentials can lead to authentication failures.
- Network issues or API downtime can cause request failures.
Error Messages:
"No data got returned": Indicates that the API response did not include expected data; verify the ticket ID and API availability.- Authentication errors: Check that the OAuth2 credentials are valid and have necessary scopes.
- Validation errors from the API: Ensure all required fields are correctly filled and formatted.
Links and References
- Teamleader API Documentation
- n8n OAuth2 Credential Setup Guide (within n8n documentation)