Actions100
- Activity Logs Actions
- Articles Actions
- Asset Layouts Actions
- Asset Passwords Actions
- Assets Actions
- Get Assets
- Get Companies Company Id Assets
- Post Companies Company Id Assets
- Get Companies Company Id Assets Id
- Put Companies Company Id Assets Id
- Delete Companies Company Id Assets Id
- Put Companies Company Id Assets Id Archive
- Put Companies Company Id Assets Id Unarchive
- Put Companies Company Id Assets Id Move Layout
- Cards Actions
- Companies Actions
- Expirations Actions
- Exports Actions
- Folders Actions
- IP Addresses Actions
- Lists Actions
- Magic Dash Actions
- Matchers Actions
- Networks Actions
- Password Folders Actions
- Procedure Tasks Actions
- Procedures Actions
- Public Photos Actions
- Rack Storage Items Actions
- Rack Storages Actions
- Relations Actions
- Uploads Actions
Overview
This node operation unarchives a company by its ID. It is useful in scenarios where companies have been previously archived (soft-deleted or hidden) and need to be restored to active status within the system. For example, if a user mistakenly archived a company record or wants to reactivate a previously inactive company, this operation will reverse that state.
Properties
Name | Meaning |
---|---|
Id | The unique numeric identifier of the company to unarchive |
Output
The output JSON contains the response from the API after attempting to unarchive the specified company. This typically includes details about the company’s current state post-unarchiving, such as confirmation of success or updated company data fields. There is no binary data output for this operation.
Dependencies
- Requires an API key credential for authentication with the external service.
- The node uses a base URL configured via credentials to connect to the API endpoint.
- Depends on the
@avantguardllc/n8n-openapi-node
package and an OpenAPI specification file (openapi.json
) bundled with the node for request building.
Troubleshooting
- Invalid Company ID: If the provided company ID does not exist or is incorrect, the API may return an error indicating the resource was not found. Verify the ID before retrying.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key or token is correctly set up in the node credentials.
- Network Issues: Connectivity problems can prevent the node from reaching the API. Check network settings and base URL configuration.
- Permission Denied: The API user might lack permissions to unarchive companies. Confirm appropriate access rights are granted.
Links and References
- Refer to the external API documentation for detailed information on the "unarchive company" endpoint.
- Consult n8n documentation on setting up API credentials and using custom nodes.