Actions43
- Earning Types Actions
- Email Templates Actions
- Employee Types Actions
- Employees Actions
- Entities Actions
- Classes Actions
- Contacts Actions
- Department Groups Actions
- Exchange Rate Lines Actions
- Exchange Rate Types Actions
- Exchange Rates Actions
- Attachment Folders Actions
- Get Next Value Actions
- Location Groups Actions
- Locations Actions
- Roles Actions
- User Groups Actions
- Users Actions
- Affiliate Entity Groups Actions
- Attachments Actions
- Departments Actions
- Document Sequences Actions
Overview
This node enables creating a new "Company Config Class" within the "Classes" resource of a company configuration system, likely integrated with Sage Intacct via AvantGuard. It is designed to facilitate the management of classification entities that organize company data such as goods, donations, or other categorizations.
Typical use cases include:
- Automating the creation of classification categories for financial or inventory items.
- Structuring company data hierarchically by defining parent-child relationships between classes.
- Managing metadata about classes such as status, descriptions, and audit information.
For example, a user might create a class called "Goods" with an ID and description to categorize all goods available for donation, enabling consistent reporting and transaction posting rules.
Properties
| Name | Meaning |
|---|---|
| Id | Unique identifier string for the class. This is required and used to uniquely identify the class in the system. |
| Name | The display name of the class. Required field representing the human-readable name of the class. |
| Additional Body Fields | Optional additional fields to enrich the class definition: - Key: System-assigned unique key identifying the class in URLs or JSON bodies. - Href: URL endpoint for this class. - Description: Text describing the class. - Status: Status of the class with options: active, activeNonPosting, inactive.- Location Key: Unique key for the entity location. - Parent: JSON object defining the parent class for hierarchical structuring. - Audit: JSON object containing audit metadata like created/modified timestamps and user IDs. |
Output
The node outputs JSON data representing the newly created Company Config Class. This JSON includes all properties sent in the request along with any additional metadata returned by the API. The output structure corresponds to the class object created on the server side.
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.
- Uses HTTP headers specifying JSON content type and acceptance.
- Depends on the external service AvantGuard's Sage Intacct API endpoint
/ia/api/v1.
Troubleshooting
- Authentication errors: Ensure the API key credential is correctly set up and has permissions to create classes.
- Validation errors: Missing required fields like
IdorNamewill cause the API to reject the request. Verify all required inputs are provided. - Invalid JSON in Parent or Audit fields: These fields expect valid JSON objects; malformed JSON strings will cause errors.
- Status field misuse: Only the specified options (
active,activeNonPosting,inactive) are accepted. Using invalid values will result in errors. - API connectivity issues: Confirm the base URL and network access to the AvantGuard Sage Intacct API.
Links and References
- Sage Intacct API Documentation
- AvantGuard n8n Integration Documentation
- JSON Schema Reference (for understanding JSON property structures)