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 is designed to update a specific key within a company configuration related to Location Groups in the AvantGuard Sage Intacct system. It allows users to modify details of a Location Group by sending an update request with specified fields. This is useful for automating updates to company location settings, such as changing identifiers or other configurable parameters tied to location groups.
Practical examples include:
- Updating the identifier of a location group when organizational changes occur.
- Automating batch updates to location group configurations based on external data sources.
- Integrating with other systems to keep location group data synchronized.
Properties
| Name | Meaning |
|---|---|
| Additional Body Fields | Optional additional fields to include in the update request body. Currently supports: - Id: The unique identifier of the location group to update. |
Output
The node outputs JSON data representing the response from the update operation on the Location Group. This typically includes confirmation of the updated fields and any metadata returned by the API. There is no indication that binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the AvantGuard Sage Intacct API.
- Needs the base URL of the API configured in credentials.
- Depends on the
@avantguardllc/n8n-openapi-nodepackage for building requests. - The node sends HTTP requests with JSON payloads and expects JSON responses.
Troubleshooting
- Missing or invalid Id: If the "Id" field is not provided or incorrect, the API will likely return an error indicating the resource was not found or the request is invalid. Ensure the correct Location Group Id is supplied.
- Authentication errors: If the API key or base URL is misconfigured, authentication failures will occur. Verify credentials are correctly set up.
- API endpoint issues: Network problems or incorrect base URLs can cause connection errors. Confirm the API endpoint is reachable.
- Invalid additional fields: Adding unsupported fields in "Additional Body Fields" may cause the API to reject the request. Use only documented fields.