Overview

This node operation interacts with the Gigstack API to stamp a draft invoice. It is useful in scenarios where a draft invoice needs to be officially stamped or validated through the API, typically as part of a workflow for managing Mexican tax-compliant invoicing. For example, after creating or updating a draft invoice, this operation can be used to finalize it by stamping it via the API.

Use Case Examples

1. Stamp a draft invoice by providing its Draft ID to finalize it for tax compliance.
2. Use in automated invoicing workflows to transition draft invoices to stamped status.

Properties

Output

JSON

• json - The response from the Gigstack API after stamping the draft invoice, typically containing the stamped invoice details or confirmation.

Dependencies

• Gigstack API key credential for authentication

Troubleshooting

• Ensure the Draft ID is valid and corresponds to an existing draft invoice; invalid IDs will cause API errors.
• Check that the API key credential is correctly configured and has permissions to stamp draft invoices.
• If the team ID is used, verify it is correct and the user has access to that team.
• Common errors include network issues, invalid parameters, or insufficient permissions, which can be resolved by verifying inputs and credentials.

Links

• Gigstack API Documentation - Stamp Draft - Official API documentation for stamping draft invoices with Gigstack.