AvantGuard - Sage Intacct (Company Configuration)

Actions43

Earning Types Actions
- Patch Objects Company Config Earning Type Key
- Create Objects Company Config Earning Type Key
Email Templates Actions
- Create Company Config Email Template
- Update Company Config Email Template Key
Employee Types Actions
- Create Company Config Employee Type
- Update Company Config Employee Type Key
Employees Actions
- Create Company Config Employee
- Update Company Config Employee Key
Entities Actions
- Create Company Config Entity
- Update Company Config Entity Key
Classes Actions
- Update Company Config Class Key
- Create Company Config Class
Contacts Actions
- Create Company Config Contact
- Update Company Config Contact Key
Department Groups Actions
- Create Company Config Department Group
- Update Company Config Department Group Key
Exchange Rate Lines Actions
- Create Company Config Exchange Rate Line
- Update Company Config Exchange Rate Line Key
Exchange Rate Types Actions
- Create Company Config Exchange Rate Type
- Update Company Config Exchange Rate Type Key
Exchange Rates Actions
- Create Company Config Exchange Rate
- Update Company Config Exchange Rate Key
Attachment Folders Actions
- Create Company Config Folder
- Update Company Config Folder Key
Get Next Value Actions
- Get Next Sequence Value
Location Groups Actions
- Create Company Config Location Group
- Update Company Config Location Group Key
Locations Actions
- Create Company Config Location
- Update Company Config Location Key
Roles Actions
- Create Company Config Role
- Update Company Config Role Key
User Groups Actions
- Create Company Config User Group
- Update Company Config User Group Key
Users Actions
- Create Company Config User
- Update Company Config User Key
Affiliate Entity Groups Actions
- Create Company Config Affiliate Entity Group
- Update Company Config Affiliate Entity Group Key
Attachments Actions
- Create Company Config Attachment
- Update Company Config Attachment Key
Departments Actions
- Create Company Config Department
- Update Company Config Department Key
Document Sequences Actions
- Create Company Config Document Sequence
- Update Company Config Document Sequence Key

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 important 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.
Additional Body Fields	Optional fields to provide extra metadata for the attachment container:
- Key	System-assigned unique key for the attachment.
- Name	Brief name describing the attachment container (e.g., "2022 tax forms").
- Description	Detailed description of the attachment container (e.g., "February invoices").
- 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 properties and any server-generated metadata. The output structure mirrors the input fields but may include additional identifiers or status information returned by the API.

If files are included, their data is expected to be base64 encoded within the files property. The node does not explicitly output binary data separately; instead, file contents are embedded as base64 strings inside the JSON.

Dependencies

Requires an API key credential for authenticating requests to the AvantGuard Sage Intacct Company Configuration API.
The node uses a base URL configured via credentials to send HTTP requests.
No other external dependencies are indicated.

Troubleshooting

Invalid or missing Id: Since Id is required, omitting it or providing an invalid value will likely cause request failures. Ensure the Id is unique and correctly formatted.
Malformed JSON in optional fields: Properties like folder, entity, files, and audit expect valid JSON strings. Improper formatting or syntax errors can cause parsing issues.
API authentication errors: If the API key credential is missing or incorrect, the node will fail to authenticate. Verify that the credential is properly set up.
File data encoding: File contents must be base64 encoded. Providing raw or incorrectly encoded data may result in upload errors.
Network or endpoint errors: Check the base URL and network connectivity if requests fail to reach the API.

Links and References

AvantGuard Sage Intacct API Documentation (example placeholder link)
n8n Documentation on Creating Custom Nodes
Base64 Encoding Reference

Note: This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.