AvantGuard - Sage Intacct (Company Configuration) icon

AvantGuard - Sage Intacct (Company Configuration)

AvantGuard - Sage Intacct (Company Configuration)

Actions43

Overview

This node integrates with the AvantGuard Sage Intacct Company Configuration API, specifically allowing users to update ("patch") earning type objects within a company's configuration. It is useful for scenarios where you need to modify specific attributes of an earning type without replacing the entire object. For example, updating the ID or other optional fields of an earning type dynamically based on workflow data.

Properties

Name Meaning
Additional Body Fields Optional additional fields to include in the request body when patching the earning type. Currently supports: Id (string) which represents the identifier of the earning type to be patched.

Output

The node outputs JSON data representing the response from the API after attempting to patch the earning type. This typically includes confirmation of the updated fields or error information if the patch failed. The output does not explicitly handle binary data.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard Sage Intacct API.
  • Needs the base URL of the API configured in the credentials.
  • Depends on the @avantguardllc/n8n-openapi-node package and the OpenAPI specification defined in openapi.json bundled with the node.

Troubleshooting

  • Common issues:

    • Missing or invalid API credentials will cause authentication failures.
    • Providing incorrect or incomplete IDs in the "Additional Body Fields" may result in errors or no changes applied.
    • Network connectivity problems can prevent reaching the API endpoint.
  • Error messages:

    • Authentication errors usually indicate invalid or missing API keys; verify credentials.
    • Validation errors from the API may indicate malformed request bodies; ensure that the "Additional Body Fields" are correctly formatted.
    • Timeout or connection errors suggest network issues; check connectivity and API availability.

Links and References

Discussion