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 update a specific company configuration location key within the "Locations" resource of an external system. It allows users to modify details related to a company's location by specifying the unique identifier and any additional fields they want to update. This node is useful in scenarios where company location data needs to be programmatically maintained or synchronized, such as updating address information, changing location-specific settings, or correcting data entries.
Practical examples include:
- Updating the address or contact details of a company location.
- Modifying configuration keys related to a location for compliance or operational reasons.
- Automating updates to multiple locations based on external data sources.
Properties
| Name | Meaning |
|---|---|
| Additional Body Fields | Optional fields to include in the update request body. Currently supports: - Id: The unique identifier of the location to update. |
Output
The node outputs JSON data representing the response from the API after attempting to update the company configuration location key. This typically includes confirmation of the updated fields, status messages, or error details if the update failed.
If the API supports binary data output (not indicated here), it would represent files or attachments related to the location update, but this node primarily deals with JSON responses.
Dependencies
- Requires an API key credential for authenticating requests to the external service.
- The base URL for the API must be configured in the credentials.
- Depends on the external AvantGuard Sage Intacct Company Configuration API endpoint
/ia/api/v1.
Troubleshooting
- Missing or invalid Id: If the
Idfield is not provided or incorrect, the API will likely return an error indicating that the location could not be found or identified. Ensure the correct location ID is supplied. - Authentication errors: If the API key or credentials are missing or invalid, authentication failures will occur. Verify that the API key credential is correctly set up.
- API connectivity issues: Network problems or incorrect base URL configurations can cause request failures. Confirm the base URL and network access.
- Invalid additional fields: Providing unsupported or incorrectly formatted additional body fields may result in validation errors from the API.
Links and References
- AvantGuard Sage Intacct API Documentation (example placeholder link)
- n8n Documentation on HTTP Request Nodes