Actions43
- Location Groups Actions
- Locations Actions
- Roles Actions
- User Groups Actions
- Users Actions
- Affiliate Entity Groups Actions
- Attachments Actions
- Classes Actions
- Contacts Actions
- Department Groups Actions
- Departments Actions
- Document Sequences Actions
- Earning Types Actions
- Email Templates Actions
- Employee Types Actions
- Employees Actions
- Entities Actions
- Exchange Rate Lines Actions
- Exchange Rate Types Actions
- Exchange Rates Actions
- Attachment Folders Actions
- Get Next Value Actions
Overview
This node is designed to create a new department within a company's configuration in the Sage Intacct system via the AvantGuard API. It allows users to define key attributes of a department such as its unique identifier, name, hierarchical parent, supervisor, status, and other optional metadata fields.
Typical use cases include automating the setup of organizational structures during company onboarding, synchronizing department data from HR or ERP systems, or programmatically managing departmental hierarchies and reporting structures.
For example, a user might create a "Software Development" department with a specific ID and assign a supervisor employee reference, enabling purchase approval routing and accurate reporting within Sage Intacct.
Properties
| Name | Meaning |
|---|---|
| Id | Unique identifier for the department (string). Required. |
| Name | Department name (string). Required. |
| Additional Body Fields | Optional additional fields to enrich the department object: |
| - Key | System-assigned unique key for the department (string). |
| - Number | Department number (string). |
| - Report Title | Department title displayed in reports (string). |
| - Parent | JSON object representing the parent department for hierarchy purposes. Example structure includes keys like key, id, name, and href. |
| - Supervisor | JSON object referencing the employee who supervises the department, used for routing approvals. Includes keys like key, id, name, and href. |
| - Status | Status of the department, controlling transaction posting and reporting usage. Options are: • Active — transactions can be posted and used in reports. • Active Non Posting — cannot post transactions but usable in reports. • Inactive — cannot be used for transactions or reports. |
| - Audit | JSON object containing audit information such as creation and modification timestamps and user IDs. |
| - Href | URL endpoint string for the department resource. |
Output
The node outputs JSON data representing the newly created department object as returned by the API. This typically includes all submitted fields along with any server-generated metadata such as unique keys, timestamps, or links.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the AvantGuard Sage Intacct Company Configuration API.
- The base URL for the API must be configured in the node credentials.
- The node uses HTTP requests with JSON payloads to communicate with the external service.
Troubleshooting
- Authentication errors: Ensure that the API key credential is correctly configured and has sufficient permissions to create departments.
- Validation errors: Missing required fields like
IdorNamewill cause the API to reject the request. Verify all mandatory properties are provided. - Invalid JSON in complex fields: Fields like
Parent,Supervisor, andAuditexpect valid JSON objects. Malformed JSON strings will cause parsing errors. - Status field misuse: Using an unsupported status value may result in errors; only the documented options should be used.
- API connectivity issues: Confirm network access to the configured base URL and that the API endpoint
/ia/api/v1is reachable.
Links and References
- Sage Intacct Official Documentation
- AvantGuard API Documentation (hypothetical link based on vendor name)