Overview
This node integrates with the Mikrotik API, allowing users to perform various operations on Mikrotik devices. Specifically, the "enable" operation under the "Default" resource enables a specified interface or feature by its ID or named parameter. This is useful for network administrators who want to automate enabling interfaces or services on Mikrotik routers directly from their workflow automation.
Practical examples include:
- Enabling a specific network interface (e.g., ether1) after configuration changes.
- Activating a service or feature that was previously disabled on the router.
Properties
| Name | Meaning |
|---|---|
| Host | The hostname or IP address of the Mikrotik device to connect to. |
| Ignore SSL Issues | Whether to ignore SSL certificate validation errors when connecting (true/false). |
| Id | The identifier or named parameter of the interface or feature to enable. Examples: *1, ether1. |
Output
The node outputs JSON data representing the result of the enable operation performed on the Mikrotik device. This typically includes confirmation of the action taken or details about the enabled interface or feature. The output does not explicitly mention binary data, so it is assumed to be purely JSON structured.
Dependencies
- Requires an API key credential for authenticating with the Mikrotik API.
- Needs network access to the specified Mikrotik host.
- The node uses internal client and state management classes to handle API communication and operation execution.
- No additional external services are required beyond the Mikrotik device itself.
Troubleshooting
- Connection issues: Ensure the Host property is correct and reachable from the n8n instance. Network firewalls or incorrect IPs can cause failures.
- SSL errors: If the Mikrotik device uses self-signed certificates, enable "Ignore SSL Issues" to bypass validation.
- Invalid Id: Providing an incorrect or non-existent interface ID or name will cause the operation to fail. Verify the exact interface names on the Mikrotik device.
- Authentication failures: Confirm that the API key credential is valid and has sufficient permissions to perform enable operations.
Common error messages might include connection timeouts, authentication errors, or invalid parameter errors. Resolving these involves checking credentials, network connectivity, and input parameters.