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 is designed to delete a company record by its unique identifier. It is useful in scenarios where you need to programmatically remove company data from a system, such as cleaning up outdated or incorrect entries, automating data management workflows, or integrating with external systems that require deletion of company records.
For example, if you maintain a CRM and want to automatically delete companies that have been marked as inactive for a long time, this node can be used within an automation workflow to perform those deletions based on company IDs.
Properties
| Name | Meaning |
|---|---|
| Id | The unique numeric identifier of the company to delete. This property is required to specify which company record should be removed. |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will include confirmation of the deletion or details about the deleted company record. The exact structure depends on the API response but generally confirms success or failure of the deletion request.
There is no indication that the node outputs binary data.
Dependencies
- Requires an API key credential for authentication to the external service managing company data.
- Needs the base URL of the API endpoint configured in the node credentials.
- Depends on the external AvantGuard WebhookSite API (as indicated by the bundled code referencing
@avantguardllc/n8n-openapi-nodeand related configuration).
Troubleshooting
Common issues:
- Providing an invalid or non-existent company ID will likely result in an error or no action.
- Missing or incorrect API credentials will cause authentication failures.
- Network connectivity problems may prevent the node from reaching the API endpoint.
Error messages:
- Authentication errors typically indicate missing or invalid API keys; verify credentials.
- "Company not found" or similar errors suggest the provided ID does not exist; check the ID value.
- Timeout or connection errors imply network issues; ensure the API base URL is reachable.
Links and References
- AvantGuard API Documentation (hypothetical link, replace with actual)
- n8n documentation on creating custom nodes