Gigstack icon

Gigstack

Interact with Gigstack API for Mexican tax-compliant invoicing and payments

Actions82

Invoice → Get Many Payment

AI-generated

Overview

This node operation retrieves multiple payment records related to invoices from the Gigstack API. It supports filtering, sorting, and pagination to manage the volume of returned data. This is useful for scenarios where users need to fetch a list of payments for reporting, reconciliation, or further processing within an automated workflow.

Use Case Examples

  1. Fetch all payment records for invoices without limit to analyze payment history.
  2. Retrieve a limited number of recent payments sorted by creation date for quick review.
  3. Filter payments by status or client ID to focus on specific subsets of payment data.

Properties

Name Meaning
Return All Whether to return all payment results or only up to a given limit.
Limit Maximum number of payment results to return when 'Return All' is false.
Filters Filters to narrow down the payment results, including status, client ID, order by field, sort direction, creation date range, and metadata key-value pairs.
Team ID Team ID for multi-team access; leave empty to use the default team.

Output

JSON

  • id - Unique identifier of the payment.
  • client
    • id - Identifier of the client associated with the payment.
  • items - List of items included in the payment, each with details such as id, quantity, and unit price.
  • automation_type - Type of automation applied to the payment.
  • allowed_payment_methods - Payment methods allowed for the payment.
  • currency - Currency used in the payment.
  • exchange_rate - Exchange rate applied to the payment.
  • send_email - Flag indicating if an email was sent for the payment.
  • emails - List of email addresses associated with the payment.
  • metadata - Additional metadata associated with the payment.

Dependencies

  • Gigstack API key credential

Troubleshooting

  • Common issues include invalid or missing API credentials, resulting in authentication errors.
  • Incorrect filter parameters may cause the API to return no results or errors; ensure filters are valid and correctly formatted.
  • Exceeding API rate limits can cause request failures; implement retry logic or reduce request frequency.
  • Errors related to team ID usage may occur if the specified team does not exist or the user lacks access; verify team ID correctness and permissions.

Links

Discussion