AvantGuard - Sage Intacct (Company Configuration) icon

AvantGuard - Sage Intacct (Company Configuration)

AvantGuard - Sage Intacct (Company Configuration)

Actions43

Overview

This node is designed to update a specific contact key within a company configuration in the "Contacts" resource. It allows users to modify details related to company contacts by specifying the contact's unique identifier and any additional fields they want to update. This functionality is useful in scenarios where company contact information needs to be programmatically maintained or synchronized, such as updating contact details in bulk from an external system or automating contact management workflows.

For example, a user might use this node to update the contact ID of a company representative after receiving updated information from a CRM system.

Properties

Name Meaning
Additional Body Fields Optional fields to include in the update request body. Currently supports:
- Id: The unique identifier of the contact to update.

Output

The node outputs JSON data representing the response from the update operation on the company configuration contact key. This typically includes confirmation of the update or the updated contact details. There is no indication that the node outputs binary data.

Dependencies

  • Requires an API key credential for authentication with the AvantGuard Sage Intacct Company Configuration API.
  • The base URL for the API must be configured in the credentials.
  • Depends on the @avantguardllc/n8n-openapi-node package and an OpenAPI specification (openapi.json) bundled with the node for request building.

Troubleshooting

  • Missing or invalid contact ID: If the "Id" field is not provided or incorrect, the API may return an error indicating that the contact could not be found or updated. Ensure the correct contact ID is supplied.
  • Authentication errors: If the API key credential is missing or invalid, the node will fail to authenticate. Verify that the API key is correctly configured.
  • API endpoint issues: If the base URL is misconfigured or the API service is down, requests will fail. Confirm the API endpoint is reachable.
  • Invalid additional fields: Adding unsupported fields in "Additional Body Fields" may cause the API to reject the request. Use only supported fields as per the API documentation.

Links and References

Discussion