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 employee key within the company configuration in the Employees resource. It allows users to modify certain fields related to an employee's configuration by sending an update request with optional additional body fields. This can be useful in scenarios where employee-related settings or identifiers need to be programmatically updated, such as syncing employee data from another system or adjusting configurations based on business rules.
Practical examples include:
- Updating an employee's unique identifier within the company configuration.
- Modifying employee-related metadata that affects company processes.
- Automating updates to employee keys during onboarding or role changes.
Properties
| Name | Meaning |
|---|---|
| Additional Body Fields | Optional fields to include in the update request body. Currently supports: - Id: A string representing the employee's identifier to update. |
Output
The node outputs JSON data representing the response from the update operation on the employee key within the company configuration. The structure typically includes confirmation of the update and any relevant details returned by the API.
If the node supports binary data output (not indicated here), it would represent files or attachments related to the employee configuration update, but this is not evident from the provided code.
Dependencies
- Requires an API key credential for authentication with the AvantGuard Sage Intacct Company Configuration API.
- Depends on the external service at the base URL specified in the credentials (
baseUrl). - Uses the
@avantguardllc/n8n-openapi-nodepackage to build properties and handle requests. - The node sends HTTP requests with JSON content type headers.
Troubleshooting
Common Issues:
- Missing or invalid API credentials will cause authentication failures.
- Providing an incorrect or empty
Idin the additional body fields may result in the update failing or no changes being applied. - Network connectivity issues to the configured base URL can prevent successful API calls.
Error Messages:
- Authentication errors typically indicate problems with the API key or permissions.
- Validation errors may occur if required fields are missing or malformed.
- API response errors should be checked for detailed messages indicating what went wrong.
To resolve these issues:
- Ensure valid and active API credentials are configured.
- Verify that the
Idfield is correctly set when updating. - Check network access and endpoint URLs.
- Review API documentation for required fields and constraints.