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 "Tickets Info" operation in this Teamleader node retrieves detailed information about a single ticket by its ID. This is useful when you want to fetch all available data for a specific support or service ticket within the Teamleader system.
Common scenarios include:
- Displaying ticket details in a dashboard or report.
- Using ticket information to trigger further automation or notifications.
- Integrating ticket data with other systems for customer support workflows.
For example, you might use this operation to get the status, subject, description, and assigned user of a particular ticket to update your CRM or notify a support agent.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the ticket to retrieve information for. This is required to specify which ticket's details should be fetched. |
Output
The output is a JSON object containing detailed information about the specified ticket. The structure corresponds to the Teamleader API response for a ticket, typically including fields such as:
- Ticket ID
- Subject
- Description
- Status
- Customer information
- Assignee details
- Creation and update timestamps
- Any other metadata related to the ticket
If multiple tickets were returned (not typical for an info operation), they would be returned as an array, but here it returns a single ticket object.
No binary data is output by this operation.
Dependencies
- Requires an active connection to the Teamleader API using OAuth2 authentication.
- The node must be configured with valid credentials that allow access to the Teamleader API.
- Network connectivity to
https://api.focus.teamleader.euis necessary.
Troubleshooting
- Missing or invalid ID: If the ID parameter is empty or incorrect, the API will not return the ticket data. Ensure the ID is correct and corresponds to an existing ticket.
- API errors: Errors from the Teamleader API (e.g., unauthorized, not found) will be thrown as node errors. Check that the OAuth2 credentials are valid and have sufficient permissions.
- No data returned: If the API responds successfully but without data, the node throws an error indicating no data was returned. Verify the ticket ID and API availability.
- Rate limits or network issues: Temporary failures may occur due to rate limiting or connectivity problems. Retrying after some time or checking network settings can help.
Links and References
- Teamleader API Documentation
- Teamleader Tickets API Reference (for detailed field descriptions)