AvantGuard - Sage Intacct (Common Services)

Actions6

Allowed Operations Actions
- List Allowed Operations
Composite Requests Actions
- Post Services Composite
Models Actions
- Get Services Model
Query Actions
- Post Services Query
User Views Actions
- Create Core User View
- Update Core User View Key

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 managed in Sage Intacct.

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 depend on permissions or capabilities tied to particular object keys.

Properties

Name Meaning

Additional Body Fields Optional fields to customize the request body sent to the API. Contains:
- Object: The object name to query, formatted as <application-name>/<object name> (e.g., accounts-payable/vendor). Required.
- Keys: JSON array of up to 1000 object keys to check allowed operations for. Required.
- Operations: JSON array specifying which operations to query. If omitted, all supported operations are returned.
- Options: JSON object with additional request options.

Name	Meaning
Additional Body Fields	Optional fields to customize the request body sent to the API. Contains: - Object: The object name to query, formatted as `<application-name>/<object name>` (e.g., `accounts-payable/vendor`). Required. - Keys: JSON array of up to 1000 object keys to check allowed operations for. Required. - Operations: JSON array specifying which operations to query. If omitted, all supported operations are returned. - Options: JSON object with additional request options.

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 API response.

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.
Needs the base URL of the Sage Intacct API configured in credentials.
Depends on the @avantguardllc/n8n-openapi-node package for OpenAPI integration.
The node sends requests to the endpoint /ia/api/v1 on the configured base URL.

Troubleshooting

Invalid Object Name: If the object property is incorrectly formatted or does not exist, the API may return errors or empty results. Ensure the object name follows the <application-name>/<object name> format exactly.
Malformed JSON in Keys or Operations: Since these properties expect JSON arrays, invalid JSON syntax will cause parsing errors. Validate JSON input carefully.
Exceeding Key Limits: The API limits keys to 1000 per request. Sending more may result in errors or truncated responses.
Authentication Failures: Missing or incorrect API credentials will prevent successful requests. Verify the API key and base URL configuration.
Empty Responses: If no operations are returned, verify that the keys exist and that the user has permission to view their allowed operations.

Links and References

AvantGuard Sage Intacct API Documentation (example placeholder link)
n8n OpenAPI Node Integration Guide