Gigstack icon

Gigstack

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

Actions82

Invoice → Get Many Egress

AI-generated

Overview

This node operation retrieves multiple egress invoices from the Gigstack API. It supports filtering, sorting, and pagination to customize the results. This is useful for scenarios where users need to fetch a list of outgoing invoices for accounting, reporting, or integration with other systems.

Use Case Examples

  1. Fetch all egress invoices created after a specific date and sort them by creation date in descending order.
  2. Retrieve a limited number of egress invoices filtered by status and client ID.

Properties

Name Meaning
Return All Whether to return all results or only up to a given limit.
Limit Maximum number of egress invoices to return when 'Return All' is false.
Filters Filters to narrow down the egress invoices by status, client ID, order, 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 egress invoice.
  • client
    • id - Client identifier associated with the invoice.
  • status - Status of the invoice (e.g., valid, canceled, pending).
  • timestamp - Creation timestamp of the invoice.
  • items - List of items included in the invoice.
  • currency - Currency used in the invoice.
  • payment_method - Payment method specified for the invoice.
  • metadata - Additional metadata associated with the invoice.

Dependencies

  • Gigstack API key credential

Troubleshooting

  • Ensure the Gigstack API key credential is correctly configured and has the necessary permissions to access invoice data.
  • If the node returns an empty list, verify that the filter criteria are correct and that there are matching egress invoices in the account.
  • Common error messages may include authentication errors (check API key), invalid filter parameters (verify filter values), and rate limiting (retry after some time).

Links

Discussion