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 "List messages" operation under the "Tickets" resource in this node allows users to retrieve a list of messages associated with a specific ticket from the Teamleader API. This is useful for scenarios where you want to review all communications or message history related to a particular support ticket or issue tracked within Teamleader.
Practical examples include:
- Fetching all messages for a ticket to display conversation history in a customer support dashboard.
- Automating workflows that analyze ticket messages for sentiment or keyword detection.
- Archiving or exporting ticket message data for reporting or compliance purposes.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the ticket whose messages you want to list. |
| Limit | The maximum number of message results to return (default is 50). |
Output
The output is a JSON array containing the messages retrieved for the specified ticket. Each element in the array represents a single message object as returned by the Teamleader API. The exact structure of each message object depends on the API response but typically includes details such as message content, sender information, timestamps, and message type.
No binary data output is indicated for this operation.
Dependencies
- Requires an OAuth2 API credential configured for Teamleader to authenticate requests.
- The node makes HTTP POST requests to the Teamleader API endpoint
https://api.focus.teamleader.euusing the path corresponding to the selected operation (tickets.listMessages). - Proper API permissions are needed to access ticket messages.
Troubleshooting
- No data returned but request was successful: This message indicates the API call succeeded but no messages were found for the given ticket ID. Verify the ticket ID is correct and that the ticket has messages.
- No data got returned: This error means the API response did not contain expected data. Check if the ticket ID exists and the API credentials have sufficient permissions.
- API errors: If the API returns an error (e.g., invalid token, permission denied), the node will throw an error unless "Continue On Fail" is enabled, in which case it outputs the error message in the result.
- Ensure the "ID" property is provided and valid; missing or incorrect IDs will cause failures.
- The "Limit" should be a positive integer; setting it too high might lead to performance issues or API rate limits.
Links and References
- Teamleader API Documentation - Official documentation for understanding the API endpoints and data structures.