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 create a new attachment folder within a company configuration system, specifically under the "Attachment Folders" resource with the operation "Create Company Config Folder." It allows users to define a unique folder by specifying an identifier and optionally adding metadata such as description, parent folder, associated entity, status, and audit information.
Common scenarios where this node is beneficial include organizing company documents, tax forms, or other files into structured folders for easier management and retrieval. For example, a user might create a folder named "2024 Taxes" to store all tax-related documents for that year, associating it with a specific entity or department within the company.
Properties
| Name | Meaning |
|---|---|
| Id | Unique name for the folder. This value cannot be changed after the folder is created. |
| Additional Body Fields | Optional additional fields to further describe or configure the folder. These include: - Key: System-assigned unique key used in URLs or JSON bodies. - Description: Text describing the folder. - Parent: JSON object representing the parent folder for hierarchy. - Entity: JSON object representing the associated entity (e.g., location or department). - Href: URL endpoint for the folder. - Status: Object status, either "Active" or "Inactive". - Audit: JSON object containing audit details like creation and modification timestamps and modifier identity. |
Output
The node outputs JSON data representing the newly created attachment folder. This JSON includes at least the properties sent in the request, such as the folder's unique ID, key, description, parent folder reference, associated entity, status, and audit information. The output structure enables downstream nodes or workflows to access the folder details for further processing or referencing.
There is no indication that the node outputs binary data.
Dependencies
- Requires an API key credential for authentication to the AvantGuard Sage Intacct Company Configuration API.
- The base URL for the API must be configured in the node credentials.
- The node sends HTTP requests with JSON payloads to the specified API endpoints.
Troubleshooting
- Missing or invalid Id: Since the folder ID is required and immutable, omitting it or providing a duplicate may cause errors. Ensure the ID is unique and correctly formatted.
- Invalid JSON in Additional Fields: The
parent,entity, andauditfields expect valid JSON objects. Malformed JSON will likely cause request failures. - API Authentication Errors: If the API key or base URL is incorrect or missing, the node will fail to authenticate. Verify credentials are properly set up.
- Status Field Issues: Only "active" or "inactive" are accepted values for the status field. Using other values may result in validation errors.
- Network or Endpoint Errors: Connectivity issues or incorrect endpoint URLs can cause request failures. Confirm network access and correct API base URL.
Links and References
- AvantGuard Sage Intacct API Documentation (hypothetical link based on context)
- n8n Documentation on Creating Custom Nodes
- JSON Schema Reference for Folder Objects
Note: The above summary is based solely on static analysis of the provided source code and property definitions.