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 interact with the "Attachment Folders" resource, specifically to update the "Company Config Folder Key". It allows users to modify certain properties of a company configuration folder by sending an update request. This can be useful in scenarios where you need to programmatically adjust folder settings or metadata related to company attachments within an integrated system.
A practical example would be updating the identifier or key associated with a company's attachment folder to reflect organizational changes or to correct data inconsistencies without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Additional Body Fields | Optional additional fields to include in the update request body. Currently supports: |
| - Id: A string representing the identifier of the folder to update. |
Output
The node outputs JSON data representing the response from the update operation on the company config folder. This typically includes confirmation of the updated fields and any relevant metadata returned by the API after the update.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authentication to the AvantGuard Sage Intacct Company Configuration API.
- The base URL for the API is configured via credentials.
- Uses HTTP headers specifying
Accept: application/jsonandContent-Type: application/json. - Depends on the external package
@avantguardllc/n8n-openapi-nodefor building request properties and handling OpenAPI specifications.
Troubleshooting
Common Issues:
- Missing or invalid API credentials will cause authentication failures.
- Providing an incorrect or non-existent folder Id in the additional body fields may result in errors indicating that the resource was not found.
- Network connectivity issues or incorrect base URL configuration can prevent successful API calls.
Error Messages:
- Authentication errors typically indicate invalid or missing API keys; verify credentials are correctly set.
- Validation errors may occur if required fields are missing or malformed; ensure the "Id" field is correctly provided.
- API response errors should be checked for detailed messages to guide corrective actions.