Teamleader icon

Teamleader

Consume Teamleader API

Actions60

Overview

The "Add reply" operation for the Tickets resource in this Teamleader node allows users to add a reply message to an existing support ticket within the Teamleader system. This is useful for customer support workflows where agents need to respond to tickets with updates, answers, or follow-up information.

Typical scenarios include:

  • Customer support teams replying to customer inquiries or issues.
  • Adding internal notes or replies visible to customers.
  • Updating the status of a ticket while adding a reply.

For example, after receiving a customer query, an agent can use this operation to post a formatted HTML reply to the ticket and optionally update the ticket's status.

Properties

Name Meaning
Body The content of the reply message. Supports HTML formatting.
Ticket Status ID (Optional) The ID of the new status to set the ticket to after adding the reply.
ID The unique identifier of the ticket to which the reply will be added.

Output

The output is a JSON array containing the response data from the Teamleader API after adding the reply. The structure typically includes details about the newly created reply message or confirmation of the action.

No binary data output is involved in 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 https://api.focus.teamleader.eu using the /tickets.addReply operation path.
  • Proper API authentication token must be available via the configured OAuth2 credentials.

Troubleshooting

  • Common Issues:

    • Missing or invalid ticket ID (ID property) will cause the API call to fail.
    • Providing an invalid or unauthorized ticket status ID may result in errors or ignored status updates.
    • Improperly formatted HTML in the Body field could lead to unexpected rendering in the ticket system.

  • Error Messages:

    • "No data got returned": Indicates that the API response did not contain expected data; verify the request parameters and API availability.
    • Network or authentication errors: Ensure the OAuth2 credentials are valid and have required scopes.
    • Validation errors from the API: Check that all required fields are provided and correctly formatted.

To resolve these, verify input parameters, ensure valid credentials, and consult Teamleader API documentation for correct usage.

Links and References

Discussion