Actions37
- Authentication Actions
- Contacts Actions
- Book Entries Actions
- Invoices Actions
- Tickets Actions
- Paysheets Actions
- Numbering Series Actions
- Accounting Categories Actions
- Accounting Subcategories Actions
- Attachments Actions
Tickets → Get Tickets
AI-generatedOverview
This node operation retrieves tickets from the Quipu API based on various filter criteria. It is useful for scenarios where users need to fetch and analyze ticket data such as invoices or expenses filtered by kind, payment status, period, contact ID, or custom field queries. For example, a user can get all paid income tickets for a specific quarter or search tickets by a custom query term.
Use Case Examples
- Fetch all paid income tickets for the first quarter of 2015.
- Search tickets related to a specific contact ID with unpaid status.
- Retrieve tickets sorted by issue date and total amount with pagination support.
Properties
| Name | Meaning |
|---|---|
| Filter Kind | Filter tickets by their kind, such as income, expenses, employee, supplier, client, or assets. |
| Filter Q | Search query string to filter tickets by matching terms. |
| Filter Period | Filter tickets by a specific period, e.g., a quarter or year. |
| Filter Payment Status | Filter tickets by their payment status such as paid, unpaid, due, or pending. |
| Filter Contact Id | Filter tickets by a specific contact ID. |
| Filter Field Query | Filter tickets by a JSON object specifying field and term queries. |
| Sort | Sort criteria for the tickets, e.g., by issue date or total amount. |
| Page Number | Page number for paginated results. |
| Include | Include related resources such as items in the ticket data. |
Output
JSON
id- Unique identifier of the ticket.kind- Kind of the ticket (income, expenses, etc.).issue_date- Date when the ticket was issued.total_amount- Total amount of the ticket.payment_status- Payment status of the ticket.contact_id- Identifier of the contact associated with the ticket.items- List of items included in the ticket, if requested.
Dependencies
- Quipu API with API key credential
Troubleshooting
- Ensure the API key credential is correctly configured and has necessary permissions to access ticket data.
- Check that the filter parameters are valid and correctly formatted, especially JSON field queries.
- If pagination is used, verify that the page number is within the valid range.
- Network issues or SSL certificate problems can cause request failures; use the 'Ignore SSL Issues' option cautiously if needed.
Links
- Quipu API Documentation - Official API documentation for Quipu, including endpoints for tickets and filtering options.