Actions12
Overview
This node integrates with the Square API to manage invoices, specifically allowing users to create new invoices associated with a given location. It is useful in scenarios where businesses want to automate invoice generation within their workflows, such as after a sale or service completion.
For example, a user can configure this node to automatically create an invoice for a customer at a specific store location, optionally including details like invoice number, description, payment requests, and recipient information.
Properties
| Name | Meaning |
|---|---|
| Location ID | The identifier of the location that the invoice will be associated with. This is required. |
| Additional Fields | A collection of optional fields to customize the invoice: |
| - Description | Text describing the invoice. |
| - Invoice Number | A unique string identifying the invoice. |
| - Payment Requests | One or more payment request entries, each containing: |
| Request Type | The type of payment request (only "Balance" is available). |
| Due Date | The due date for the payment request. |
| Tipping Enabled | Boolean flag indicating if tipping is enabled for this payment request. |
| - Primary Recipient | Details about the primary recipient of the invoice: |
| Customer ID | The identifier of the customer who will receive the invoice. |
| - Title | The title of the invoice. |
Output
The node outputs JSON data representing the response from the Square API after creating the invoice. This typically includes all details of the newly created invoice such as its ID, status, associated location, payment requests, recipients, and timestamps.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Square API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The base URL used depends on the environment setting (sandbox or production).
Troubleshooting
- Missing Required Fields: If the
Location IDis not provided, the node will fail because it is mandatory. - API Errors: Errors returned by the Square API (e.g., invalid IDs, permission issues) will be surfaced. Users should verify that the API key has appropriate permissions and that all IDs are correct.
- Empty Additional Fields: While additional fields are optional, providing invalid or malformed data may cause errors.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output.