Actions43
- Earning Types Actions
- Email Templates Actions
- Employee Types Actions
- Employees Actions
- Entities Actions
- Classes Actions
- Contacts Actions
- Department Groups Actions
- Exchange Rate Lines Actions
- Exchange Rate Types Actions
- Exchange Rates Actions
- Attachment Folders Actions
- Get Next Value Actions
- Location Groups Actions
- Locations Actions
- Roles Actions
- User Groups Actions
- Users Actions
- Affiliate Entity Groups Actions
- Attachments Actions
- Departments Actions
- Document Sequences Actions
Overview
This node is designed to retrieve the next sequence value for a document sequence in a system, typically used for generating unique identifiers or incremental numbers. It is useful in scenarios where you need to maintain sequential numbering for documents such as invoices, orders, or any other records that require a consistent and unique sequence.
For example, if you have an invoice system that needs to assign invoice numbers automatically, this node can fetch the next available invoice number based on the configured document sequence key, ID, and optionally the fiscal year.
Properties
| Name | Meaning |
|---|---|
| Additional Body Fields | Optional fields to customize the request body when fetching the next sequence value. Includes: |
| - Key | Document sequence key (string) used to identify the sequence. |
| - Id | Document sequence ID (string) representing the specific sequence to increment. |
| - Fiscal Year | Fiscal year (number) for which the sequence applies; has effect only if fiscal year rollover is enabled. |
Output
The node outputs JSON data containing the next sequence value retrieved from the external system. The exact structure depends on the API response but generally includes the new sequence number or identifier.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authentication with the external service.
- Needs configuration of the base URL for the API endpoint.
- Depends on the external system's API that manages document sequences.
Troubleshooting
Common issues:
- Incorrect or missing API credentials will cause authentication failures.
- Providing invalid or non-existent sequence keys or IDs may result in errors or empty responses.
- Fiscal year values outside the supported range or when rollover is disabled might be ignored or cause unexpected results.
Error messages:
- Authentication errors: Verify API key and permissions.
- "Sequence not found" or similar: Check that the key and ID are correct and exist in the system.
- Network or timeout errors: Ensure connectivity to the API endpoint and that the base URL is correctly configured.
Links and References
- Refer to your external system’s API documentation for details on document sequences and their parameters.
- n8n documentation on creating and using custom nodes for API integrations.