Actions67
- User Actions
- Teams Actions
- Custom Fields Actions
- Tickets Actions
- Ticket Status 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
- Notes Actions
Tickets → Info
AI-generatedOverview
This node operation retrieves detailed information for a single ticket from the Teamleader API. It is useful in scenarios where you need to fetch specific ticket data, such as status, subject, description, and related customer information, for further processing or display in workflows.
Use Case Examples
- Fetching ticket details to display in a customer support dashboard.
- Retrieving ticket information to automate follow-up actions based on ticket status.
Properties
| Name | Meaning |
|---|---|
| ID | The ID of the ticket to retrieve information for. |
Output
JSON
id- The unique identifier of the ticket.subject- The subject or title of the ticket.description- Detailed description of the ticket.status- Current status of the ticket.customer- Information about the customer related to the ticket.assignee- User assigned to the ticket.created_at- Timestamp when the ticket was created.updated_at- Timestamp when the ticket was last updated.
Dependencies
- Teamleader API accessed via OAuth2 authentication
Troubleshooting
- Ensure the ticket ID provided is valid and exists in the Teamleader system.
- Check that the OAuth2 credentials are correctly configured and have the necessary permissions to access ticket information.
- Common error: 'No data got returned' indicates the ticket ID might be incorrect or the ticket does not exist.
Links
- Teamleader API Documentation - Official documentation for the Teamleader API, including endpoints for tickets.