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 tickets and their messages. Specifically, for the "Tickets" resource and the "Add internal message" operation, it allows users to add an internal message to an existing ticket in Teamleader. This is useful for adding private notes or internal communications related to a ticket that are not visible to the customer.
Common scenarios include:
- Customer support teams adding internal comments or updates on a ticket without notifying the customer.
- Internal collaboration where team members share information about the ticket status or troubleshooting steps.
- Logging internal decisions or actions taken on a ticket for audit or tracking purposes.
Example: Adding an internal message to a ticket with ID 12345 to note that the issue requires escalation.
Properties
| Name | Meaning |
|---|---|
| Body | The content of the internal message to add. Supports HTML formatting. |
| Ticket Status ID | (Optional) The ID of the new status to set the ticket to after adding the internal message. |
| ID | The unique identifier of the ticket to which the internal message will be added. |
Output
The node outputs a JSON array containing the response data from the Teamleader API after adding the internal message. The structure corresponds to the API's response for the created internal message object, typically including details such as message ID, body, creation timestamp, and associated ticket ID.
No binary data output is produced by this operation.
Dependencies
- Requires an OAuth2 API credential configured for Teamleader with appropriate permissions to manage tickets.
- The node makes HTTP POST requests to the Teamleader API endpoint at
https://api.focus.teamleader.eu. - The user must have valid authentication tokens and API access rights to perform ticket modifications.
Troubleshooting
- No data returned but request was successful: This indicates the API call succeeded but returned no data. Verify that the ticket ID is correct and that the API supports returning data for this operation.
- No data got returned: The API response did not contain expected data. Check if the ticket exists and the user has permission to add internal messages.
- Authentication errors: Ensure the OAuth2 credentials are valid and have not expired.
- Invalid ticket ID: Confirm the ticket ID provided exists in Teamleader.
- Empty or invalid Body: The "Body" property is required; ensure it contains valid HTML-formatted text.
Links and References
- Teamleader API Documentation
- Teamleader Tickets API section (for detailed API endpoints and payloads)