Actions82
- Client Actions
- Invoice Actions
- Payment Actions
- Receipt Actions
- Service Actions
- Team Actions
- User Actions
- Webhook Actions
- Descarga Masiva (SAT) Actions
Client → Stamp Pending Receipts
AI-generatedOverview
This node operation interacts with the Gigstack API to stamp all pending receipts for a specified client. It is useful in scenarios where a user needs to automate the process of stamping multiple receipts that are pending for a client, ensuring compliance with Mexican tax regulations. For example, a business can use this operation to batch process and stamp all pending receipts for a client at once, saving time and reducing manual effort.
Use Case Examples
- Stamp all pending receipts for a client identified by their Client ID to ensure all receipts are properly stamped and compliant.
- Automate the stamping process for pending receipts in a workflow that manages client invoicing and payments.
Properties
| Name | Meaning |
|---|---|
| Client ID | The ID of the client for whom the pending receipts will be stamped. |
| Team ID | Optional Team ID for Gigstack Connect to specify multi-team access. Leave empty to use the default team. |
Output
JSON
json- The response from the Gigstack API after stamping pending receipts, typically containing status or confirmation details.
Dependencies
- Gigstack API key credential for authentication
Troubleshooting
- Ensure the Client ID is valid and exists in the Gigstack system to avoid errors.
- Verify that the API key credential is correctly configured and has the necessary permissions to perform stamping operations.
- If the operation fails, check for network issues or API rate limits that might prevent successful stamping.