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 integrates with the AvantGuard Sage Intacct Company Configuration API, specifically allowing users to update ("patch") earning type objects within a company's configuration. It is useful for scenarios where you need to modify specific attributes of an earning type without replacing the entire object, such as updating identifiers or other optional fields dynamically.
Practical examples include:
- Updating the ID of an existing earning type.
- Adding or modifying optional fields related to earning types in a company’s payroll or accounting setup.
Properties
| Name | Meaning |
|---|---|
| Additional Body Fields | Optional additional fields to include in the PATCH request body. Currently supports: Id (string) which represents the identifier of the earning type to patch. |
Output
The node outputs JSON data representing the response from the PATCH request to the Sage Intacct API. This typically includes the updated earning type object or confirmation of the successful update. The output does not explicitly handle binary data.
Dependencies
- Requires an API key credential for authenticating with the AvantGuard Sage Intacct API.
- Needs the base URL of the Sage Intacct API configured in credentials.
- Depends on the
@avantguardllc/n8n-openapi-nodepackage and the OpenAPI specification (openapi.json) bundled with the node for request building.
Troubleshooting
- Authentication errors: Ensure that the API key credential is correctly set up and has sufficient permissions to patch earning types.
- Invalid field errors: When adding additional body fields, verify that the field names and values conform to the API schema; otherwise, the API may reject the request.
- Network or connectivity issues: Confirm that the base URL is correct and accessible from the n8n environment.
- Empty or missing required fields: The node expects at least the
idfield when patching an earning type; omitting it may cause errors.