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 operation, Create Company Config Attachment, allows users to create an attachment container within a company configuration system. It is useful for organizing and storing files related to company configurations, such as tax forms, invoices, or other relevant documents. The node supports specifying metadata about the attachment container, associating it with folders or entities, and including multiple files.
Practical examples:
- Uploading and categorizing monthly tax documents for a company.
- Storing invoice attachments linked to specific departments or entities within the company.
- Organizing compliance-related documents in designated folders for easy retrieval.
Properties
| Name | Meaning |
|---|---|
| Id | Unique identifier for the attachment container (required). |
| Additional Body Fields | Optional fields to provide extra metadata about the attachment container: |
| - Key | System-assigned unique key for the attachment. |
| - Name | Brief name describing the attachment container. |
| - Description | Detailed description of the attachment container. |
| - Href | URL endpoint representing the attachment container. |
| - Folder | JSON object defining the folder where this attachment resides, including its key, id, and href. |
| - Entity | JSON object representing the entity associated with the attachment, including key, id, name, href. Attachments at top level have null values here. |
| - Files | JSON array of file objects contained in the attachment. Each file includes properties like key, id, href, name, size, base64-encoded data, and attachment reference. |
| - Audit | JSON object containing audit information such as createdDate, modifiedDate, createdBy, and modifiedBy. |
Output
The node outputs JSON data representing the newly created attachment container, including all specified metadata and file details. This output can be used downstream in workflows to confirm creation, log information, or trigger further processing.
If files are included, their content is expected to be base64-encoded within the data field of each file object. The node does not explicitly mention binary output handling, so file data is managed as encoded JSON strings.
Dependencies
- Requires an API key credential for authentication to the AvantGuard Sage Intacct Company Configuration API.
- The base URL for API requests is configured via credentials.
- The node uses HTTP requests with JSON payloads to interact with the external service.
Troubleshooting
- Missing required Id: The node requires the "Id" property; omitting it will likely cause an error from the API.
- Invalid JSON in fields: Properties like Folder, Entity, Files, and Audit expect valid JSON strings. Malformed JSON will cause parsing errors.
- Authentication failures: Ensure the API key credential is correctly set up and has necessary permissions.
- File data encoding: File contents must be base64-encoded strings; incorrect encoding may lead to upload failures.
- API endpoint issues: Verify that the base URL and endpoints are correct and accessible.
Links and References
- AvantGuard Sage Intacct API Documentation (example placeholder, replace with actual if available)
- n8n documentation on Creating Custom Nodes