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 interacts with the Teamleader API to perform various operations on different resources. Specifically, for the Tickets resource and the Get message operation, it retrieves a single message associated with a ticket by its message ID. This is useful in scenarios where you want to fetch detailed information about a specific message within a support or service ticket, such as viewing customer replies or internal notes.
Practical examples include:
- Fetching the content of a particular message in a ticket to display or process it further.
- Integrating ticket messages into other systems like CRM or helpdesk tools.
- Automating workflows that require message details for notifications or analytics.
Properties
| Name | Meaning |
|---|---|
| Message ID | The unique identifier of the message to retrieve from the ticket. This is required. |
Output
The node outputs JSON data representing the requested ticket message. The structure corresponds to the message object returned by the Teamleader API, typically including fields such as message content, sender information, timestamps, and related metadata.
If multiple items are processed, the output is an array of such message objects.
No binary data output is indicated for this operation.
Dependencies
- Requires an OAuth2 API credential configured for Teamleader with appropriate permissions.
- The node makes HTTP POST requests to the Teamleader API endpoint
https://api.focus.teamleader.euusing the specified operation path. - The environment must have internet access to reach the Teamleader API.
Troubleshooting
- No data returned but request was successful: This indicates the API call succeeded but no message data was found. Verify the provided Message ID is correct and exists.
- No data got returned: The API response did not contain expected data. Check if the Message ID is valid and the ticket/message still exists.
- API errors: Errors from the Teamleader API (e.g., authentication failure, invalid parameters) will be thrown as node errors. Ensure the OAuth2 credentials are valid and have necessary scopes.
- Continue on Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error messages in the output.
Links and References
- Teamleader API Documentation
- Teamleader Tickets API Reference (for detailed message object schema)