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 records in bulk or integrating with external CRM systems.

For example, a user might use this node to update the contact ID of a company configuration after receiving new contact details from an external source.

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 updated contact details or status messages indicating success or failure. There is no indication that binary data is output by this node.

Dependencies

  • Requires an API key credential for authentication with the AvantGuard Sage Intacct Company Configuration API.
  • The base URL for the API is configured via credentials.
  • The node uses HTTP requests with JSON payloads to communicate with the external service.

Troubleshooting

  • Missing or invalid Id: If the "Id" field is not provided or incorrect, the update will fail. Ensure the contact ID is valid and exists in the system.
  • Authentication errors: If the API key credential is missing or invalid, the node will not authenticate successfully. Verify the API key and its permissions.
  • API endpoint issues: Network problems or incorrect base URL settings can cause failures. Confirm the base URL is correctly set in credentials.
  • Unexpected response format: If the API changes its response structure, the node may not handle it properly. Check for updates to the API or node implementation.

Links and References

Discussion