AvantGuard - Sage Intacct (Common Services) icon

AvantGuard - Sage Intacct (Common Services)

AvantGuard - Sage Intacct (Common Services)

Actions6

Overview

This node interacts with the AvantGuard Sage Intacct API to list allowed operations on specified objects within the system. It is useful for scenarios where you need to programmatically determine what actions (operations) are permitted on certain data objects, such as vendor accounts or other financial entities, based on your current permissions or configuration.

Practical examples include:

  • Retrieving the set of allowed operations for a batch of vendor records before attempting updates.
  • Filtering UI options dynamically based on what operations are available for specific objects.
  • Automating workflows that adapt their behavior depending on the allowed operations returned by the API.

Properties

Name Meaning
Additional Body Fields Optional fields to customize the request body:
- Object The object name to query, formatted as <application-name>/<object name>. Example: accounts-payable/vendor. (required)
- Keys JSON array of up to 1000 object keys for which to retrieve allowed operations. (required)
- Operations JSON array listing specific operations to query. If omitted, all supported operations will be included in the response.
- Options JSON object containing additional options for the request.

Output

The node outputs JSON data representing the allowed operations for the specified objects and keys. The structure typically includes details about each key and the operations permitted on it according to the queried parameters.

If binary data were involved, it would be summarized here, but this node deals exclusively with JSON responses describing allowed operations.

Dependencies

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

Troubleshooting

  • Invalid or missing object name: Ensure the Object property is correctly formatted as <application-name>/<object name>.
  • Malformed JSON in keys, operations, or options: Validate JSON syntax carefully; parsing errors will cause the request to fail.
  • Exceeding keys limit: The API supports up to 1000 keys per request; exceeding this may result in errors.
  • Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
  • Empty or unexpected responses: Confirm that the requested objects and keys exist and that the user has permission to view their allowed operations.

Links and References

Discussion