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 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 for this node include organizing company documents, tax forms, or other files into structured folders that reflect the company's hierarchy or entities. For example, a user might create a folder named "2024 Taxes" to store all tax-related documents for the year 2024, associating it with a specific entity or parent folder to maintain organization.
Properties
| Name | Meaning |
|---|---|
| Id | Unique name for the folder. This value cannot be changed after the folder is created. Example: "2024 Taxes" |
| 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 (e.g., "88").- Description: Text describing the folder (e.g., "2024 tax forms").- Parent: JSON object representing the parent folder for hierarchical structuring. - Entity: JSON object representing the entity associated with the folder; top-level folders may have null values. - Href: URL endpoint for the folder. - Status: Object status, either "active" (fully functional) or "inactive" (hidden and unusable).- 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, potentially enriched with server-generated fields such as unique keys or URLs. The output structure reflects the folder's metadata and hierarchical relationships.
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 uses JSON-formatted requests and expects JSON responses from the API.
Troubleshooting
Issue: Folder creation fails due to duplicate
Id.
Resolution: Ensure theIdprovided is unique and not already used by another folder, as it cannot be changed once set.Issue: Invalid JSON format in
Parent,Entity, orAuditfields.
Resolution: Verify that these fields contain valid JSON strings before sending.Issue: Missing or invalid API credentials.
Resolution: Confirm that the API key credential is correctly configured and has necessary permissions.Error Message: "Object status inactive" when trying to use an inactive folder.
Resolution: Set theStatusproperty to"active"to make the folder usable.
Links and References
- AvantGuard Sage Intacct API Documentation (hypothetical link based on context)
- n8n Documentation on Creating Custom Nodes