Actions82
- Client Actions
- Invoice Actions
- Payment Actions
- Receipt Actions
- Service Actions
- Team Actions
- User Actions
- Webhook Actions
- Descarga Masiva (SAT) Actions
Payment → Get Many
AI-generatedOverview
This node operation retrieves multiple payment records from the Gigstack API. It supports fetching all payments or limiting the number of results returned. Users can apply various filters such as payment status, client ID, client email, currency, order by fields, sort direction, creation date range, and metadata key-value pairs to refine the search results. This operation is useful for scenarios where users need to list or analyze payments, generate reports, or synchronize payment data with other systems.
Use Case Examples
- Retrieve all payments with status 'Succeeded' for a specific client email.
- Fetch up to 50 payments created after a certain date, sorted by creation timestamp in descending order.
- Filter payments by currency (e.g., USD) and metadata fields for detailed reporting.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all payment results or only up to a specified limit. |
| Limit | Maximum number of payment results to return when 'Return All' is false. |
| Filters | Collection of filters to refine the payment search results, including status, client ID, client email, currency, order by field, sort direction, creation date range, and metadata filters. |
| Team ID | Team ID for multi-team access in Gigstack Connect. Leave empty to use the default team. |
Output
JSON
id- Unique identifier of the payment.clientid- Identifier of the client associated with the payment.
status- Current status of the payment (e.g., succeeded, canceled).currency- Currency used in the payment.amount- Amount of the payment.timestamp- Timestamp when the payment was created.metadata- Additional metadata associated with the payment.
Dependencies
- Gigstack API
- An API key credential for authentication
Troubleshooting
- Ensure the API key credential is correctly configured and has the necessary permissions to access payment data.
- Verify that the filters used are valid and supported by the Gigstack API to avoid errors.
- If the node returns an error about limits, check the 'Limit' property and adjust it within the allowed range (1-100).
- Network or API downtime may cause request failures; retry or check the Gigstack service status.
Links
- Gigstack API - Payments Get Many - Official documentation for retrieving multiple payments via the Gigstack API.