Actions43
- Location Groups Actions
- Locations Actions
- Roles Actions
- User Groups Actions
- Users Actions
- Affiliate Entity Groups Actions
- Attachments Actions
- Classes Actions
- Contacts Actions
- Department Groups Actions
- Departments Actions
- Document Sequences Actions
- Earning Types Actions
- Email Templates Actions
- Employee Types Actions
- Employees Actions
- Entities Actions
- Exchange Rate Lines Actions
- Exchange Rate Types Actions
- Exchange Rates Actions
- Attachment Folders Actions
- Get Next Value 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, purchase orders, or any other records that require a consistent and unique sequence.
For example, if you have an accounting system that issues invoice numbers, this node can be used to fetch the next available invoice number automatically, ensuring no duplicates and maintaining order.
Properties
| Name | Meaning |
|---|---|
| Additional Body Fields | Optional fields to include in the request body when fetching the next sequence value. These include: |
| - Key | Document sequence key (string) |
| - Id | Document sequence ID (string) |
| - Fiscal Year | Fiscal year (number). This affects the sequence only if fiscal year rollover is enabled for the sequence. |
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 generated.
If the node supports binary data output, it would typically represent associated files or attachments related to the sequence, but based on the provided code and properties, the primary output is JSON with the sequence information.
Dependencies
- Requires an API key credential for authentication to 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:
- Missing or invalid API credentials will cause authentication failures.
- Incorrect or missing required fields like
KeyorIdmay result in errors or empty responses. - Fiscal year values outside the expected range might not affect the sequence or cause unexpected results if rollover is enabled.
Error Messages:
- Authentication errors: Check API key validity and permissions.
- Validation errors: Ensure all required fields are correctly set.
- Network errors: Verify connectivity and correct API base URL.
Links and References
- Refer to your external system’s API documentation for details on document sequence management.
- n8n documentation on how to configure API credentials and HTTP request nodes.