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 company configuration entity key within the "Entities" resource, specifically supporting the "Update Company Config Entity Key" operation. It allows users to modify certain fields of a company configuration by sending an update request with optional additional body fields.
Common scenarios for this node include automating updates to company settings or configurations in an external system that manages company entities, such as adjusting identifiers or metadata related to company profiles. For example, a user might update the ID of a company configuration entity dynamically based on workflow data.
Properties
| Name | Meaning |
|---|---|
| Additional Body Fields | Optional fields to include in the update request body. Currently supports: - Id: A string representing the identifier of the entity to update. |
Output
The node outputs JSON data representing the response from the update operation on the company configuration entity. This typically includes confirmation of the updated fields or the updated entity's details as returned by the API.
No binary data output is indicated in the source code.
Dependencies
- Requires an API key credential for authentication with the external service.
- The base URL for the API is configured via credentials and used as the request base URL.
- Depends on the
@avantguardllc/n8n-openapi-nodepackage for building properties and handling OpenAPI specifications. - Uses an OpenAPI specification file (
openapi.json) bundled with the node to define available operations and properties.
Troubleshooting
- Missing or invalid API credentials: Ensure that the API key or authentication token is correctly set up in the node credentials.
- Invalid or missing 'Id' field: The update operation requires the entity ID to identify which company configuration to update. Make sure this field is provided and valid.
- API endpoint errors: Check the base URL and network connectivity to the external API service.
- Unexpected response format: If the API changes its response structure, the node may not parse it correctly; verify compatibility with the current API version.
Links and References
- No direct external links are provided in the source code.
- Refer to the external API documentation of the company configuration service for detailed information on the update operation and supported fields.