Actions109
- 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
- Websites Actions
- Procedures Actions
- Public Photos Actions
- Rack Storage Items Actions
- Rack Storages Actions
- Relations Actions
- Uploads Actions
- Users Actions
- Activity Logs Actions
- Articles Actions
Overview
The "Delete Matcher By Id" operation for the "Matchers" resource in this custom n8n node allows users to delete a specific Matcher by providing its unique ID. This is useful in scenarios where you need to programmatically remove a Matcher from your system, such as cleaning up obsolete rules or automating maintenance tasks.
Practical examples:
- Automatically deleting Matchers that are no longer needed after a workflow completes.
- Removing test or temporary Matchers as part of a CI/CD pipeline.
- Enabling users to manage their Matcher configurations directly from n8n without manual intervention.
Properties
| Name | Type | Meaning |
|---|---|---|
| Id | Number | The ID of the Matcher to delete. (Required) |
Output
The output will typically be a JSON object reflecting the result of the deletion operation. While the exact structure depends on the API's response, it usually includes confirmation of deletion or relevant status information.
Example output:
{
"success": true,
"message": "Matcher deleted successfully."
}
If the node supports binary data output, it would only be used for error messages or logs, not for this operation.
Dependencies
- External Service: Requires access to the AvantGuard Hudu API.
- API Key/Credentials: Needs valid
avantguardHuduApicredentials configured in n8n. - Environment Variable: The base URL for the API must be set in the credentials (
baseUrl).
Troubleshooting
Common Issues:
- Invalid or missing ID: If the provided ID does not exist or is not specified, the API may return an error indicating that the Matcher was not found.
- Authentication errors: If the API key or credentials are incorrect or missing, you may receive authentication or authorization errors.
- Network issues: Connectivity problems with the API endpoint can cause request failures.
Common Error Messages and Resolutions:
"Matcher not found": Ensure the ID is correct and the Matcher exists."Unauthorized"or"Invalid API Key": Check your API credentials in n8n."Connection timed out": Verify network connectivity and the correctness of the API base URL.