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 operation creates a new Location Group within a company's configuration in Sage Intacct. Location Groups are used to organize and group multiple locations for reporting, management, or operational purposes. This is particularly useful for companies that manage multiple warehouses, offices, or other physical sites and want to categorize them logically.
Typical use cases include:
- Creating a group of warehouses in a specific region to simplify inventory reporting.
- Defining groups of locations for financial reporting where grouped locations appear as rows or columns.
- Managing contact assignments or filters on location groups for operational workflows.
For example, you might create a "Western Region Warehouses" group with ID "WH1" that includes all warehouse locations in the western US, optionally filtered by active status or sorted by custom criteria.
Properties
| Name | Meaning |
|---|---|
| Id | Location group ID, a unique identifier displayed alongside the group name in Sage Intacct. Cannot be changed after creation. |
| Name | The display name of the location group shown together with the ID. |
| Additional Body Fields | Optional additional fields to customize the location group: |
| - Key | System-assigned unique key for the location group. |
| - Href | URL endpoint for the location group. |
| - Description | Text description of the location group. |
| - Primary Contact | Default contact assigned to this group, provided as a JSON object with key, id, and href. |
| - Group Type | Membership type of the group; options are: • specific - Specify exact locations and order via groupMembers.• all - Include all locations matching the memberFilter. |
| - Member Filter | JSON filter applied when groupType is all, defining criteria such as status, total due, or name contains, to select members dynamically. |
| - Group Members | JSON array listing specific members and their sort order, applicable only when groupType is specific. |
| - Is Dimension Structure | Boolean indicating if the group should be treated as a dimension structure, allowing it to be added to rows or columns in financial reports. |
| - Audit | JSON object containing audit information like creation and modification timestamps and user IDs. |
Output
The node outputs JSON data representing the created Location Group object as returned by the Sage Intacct API. This typically includes all submitted fields along with system-generated metadata such as keys, URLs, and audit info.
If binary data were involved (not indicated here), it would represent file attachments or similar content, but this operation deals solely with JSON data.
Dependencies
- Requires an API key credential for authenticating with the Sage Intacct Company Configuration API.
- The base URL for the API must be configured in the node credentials.
- The node uses JSON payloads sent over HTTP POST to the
/ia/api/v1endpoint of the Sage Intacct service.
Troubleshooting
- Invalid or missing required fields: Ensure that both
IdandNameare provided and valid, as they are mandatory. - JSON parsing errors: Fields like
primaryContact,memberFilter,groupMembers, andauditexpect valid JSON strings. Invalid JSON will cause errors. - API authentication failures: Verify that the API key credential is correctly set up and has permissions to create location groups.
- Incorrect
groupTypeusage: When usinggroupType=all, ensurememberFilteris properly defined; whenspecific, provide validgroupMembers. - Immutable ID error: Attempting to change an existing location group's ID will fail since IDs cannot be modified after creation.
Links and References
- Sage Intacct Location Groups Documentation (hypothetical link for reference)
- n8n Documentation on Custom Nodes
- JSON Schema and Filtering Examples