AvantGuard - Sage Intacct (Company Configuration)

Overview

This node is designed to update a specific company configuration location key within the "Locations" resource of an external system, likely related to Sage Intacct company configurations. It allows users to modify details of a location by specifying its unique identifier and any additional fields they want to update.

Common scenarios for this node include:

• Updating location information such as address or identifiers in a company's configuration.
• Automating changes to location data based on business rules or external triggers.
• Integrating with other systems to keep location data synchronized.

For example, a user might use this node to update the ID of a location after receiving new location data from another system or to correct an existing location's configuration.

Properties

Output

The node outputs JSON data representing the response from the API after attempting to update the location key. This typically includes confirmation of the updated fields or error messages if the update failed.

If the API returns binary data (not indicated here), it would represent associated files or attachments related to the location, but this node primarily deals with JSON responses.

Dependencies

• Requires an API key credential for authentication with the external Sage Intacct Company Configuration API.
• Needs the base URL of the API configured in the credentials.
• Depends on the @avantguardllc/n8n-openapi-node package for building properties and handling requests.
• The node sends HTTP requests with JSON payloads to the endpoint /ia/api/v1.

Troubleshooting

• Missing or invalid Id: If the "Id" field is not provided or incorrect, the API will likely return an error indicating that the location could not be found or identified. Ensure the Id is accurate and corresponds to an existing location.
• Authentication errors: If the API key or base URL is misconfigured, the node will fail to authenticate. Verify credentials and endpoint URLs.
• API response errors: The node may throw errors if the API rejects the update due to validation issues or server problems. Check the returned error message for details.
• Empty additional fields: If no additional fields are provided, the update request might do nothing or cause an error depending on the API behavior. Always provide at least one field to update.

Links and References

• Sage Intacct API Documentation
• n8n Documentation on Creating Custom Nodes
• AvantGuard n8n OpenAPI Node Package (for reference on property builder usage)