Overview
This node integrates with the Mikrotik API, allowing users to perform various operations on Mikrotik devices. Specifically, the "add" operation under the "Default" resource enables creating new records on the device by sending parameters and special options.
Common scenarios include automating network device configuration, adding firewall rules, or managing routing tables programmatically. For example, a user might add a new IP address or a firewall filter rule by specifying relevant parameters through this node.
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 (useful for self-signed certs). |
| Properties | Key-value pairs representing parameters to apply to the newly created record. |
| Special Parameters | Additional optional fields affecting the creation behavior: |
| - Copy-from | Identifier of an existing record to copy properties from. |
| - Place-before | Identifier of a record before which the new record should be placed. |
| - Disabled | Mark the new record as disabled if set. |
| - Comment | A comment string to attach to the new record. |
Output
The node outputs JSON data representing the response from the Mikrotik API after attempting to add the new record. This typically includes details about the created entity or any error messages returned by the API.
If the API returns binary data (unlikely in this context), it would be included accordingly, but the main output is structured JSON reflecting the operation result.
Dependencies
- Requires an API key credential for authenticating with the Mikrotik device.
- Needs network access to the specified Mikrotik host.
- Supports ignoring SSL issues via a boolean flag for environments with self-signed certificates.
- Uses internal helper classes for HTTP requests, state management, operation resolution, and execution.
Troubleshooting
- Connection failures: Ensure the Host is reachable and the API credentials are correct.
- SSL errors: If using self-signed certificates, enable "Ignore SSL Issues" to bypass validation.
- Invalid parameters: Verify that all required parameters in "Properties" are correctly named and valid for the Mikrotik API.
- API errors: Check the output JSON for error messages returned by the Mikrotik API; these often indicate misconfiguration or permission issues.
- Empty or missing output: Confirm that the node received input data and that the operation was properly selected.