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 enables the creation of a new company configuration location within a system, typically used for managing organizational locations in accounting or ERP software. It is beneficial when you need to programmatically add detailed location data such as offices, warehouses, or branches into your company's configuration setup.
Practical examples include:
- Automating the onboarding process of new office locations with all relevant details.
- Integrating location data from external systems into your accounting platform.
- Maintaining up-to-date location hierarchies and contact information for reporting and operational purposes.
Properties
| Name | Meaning |
|---|---|
| Id | Unique identifier for the location. |
| Name | Name of the location. |
| Additional Body Fields | Optional additional fields to enrich the location data: |
| - Key | System-assigned unique key for the location, used in URLs or JSON bodies for operations on the location. |
| - Href | URL endpoint for this location. |
| - Status | Status of the location, indicating if it is active, active but non-posting, or inactive. Options: active, activeNonPosting, inactive. |
| - Tax Id | State tax ID or VAT registration number. |
| - Start Date | Start date of operation at this location (format: YYYY-MM-DD). |
| - End Date | End date of operation at this location (format: YYYY-MM-DD). |
| - Contacts | JSON object listing contacts related to the location, including primary and shipping contacts with detailed personal and address information. |
| - Location Reporting Title | Additional descriptive title for reports, e.g., including address or manager name. |
| - Parent | JSON object representing the parent location for hierarchical structuring. |
| - Manager | JSON object representing the employee managing the location. |
| - Audit | JSON object containing audit information such as creation and modification timestamps and user IDs. |
Output
The node outputs JSON data representing the newly created location object as returned by the API. This includes all submitted fields along with any additional metadata or identifiers assigned by the backend system.
If binary data were involved (not indicated here), it would typically represent files or attachments related to the location, but this node focuses solely on JSON data.
Dependencies
- Requires an API key credential for authentication with the target service.
- The base URL for the API must be configured in the node credentials.
- Depends on the external AvantGuard Sage Intacct Company Configuration API endpoint
/ia/api/v1.
Troubleshooting
- Missing Required Fields: Ensure that both "Id" and "Name" are provided; these are mandatory.
- Invalid JSON in Complex Fields: Fields like "contacts", "parent", "manager", and "audit" expect valid JSON strings. Malformed JSON will cause errors.
- Status Field Validation: Only the specified status options (
active,activeNonPosting,inactive) are accepted. - API Authentication Errors: Verify that the API key credential is correctly set and has sufficient permissions.
- Date Format Issues: Dates should follow the ISO format
YYYY-MM-DD; incorrect formats may lead to rejection by the API.