Wazend API icon

Wazend API

Interact with Wazend API

Actions59

Overview

This node interacts with the Wazend API to manage proxy settings for instances. Specifically, it supports defining (setting) a proxy configuration or verifying (checking) the current proxy status of an instance. This is useful in scenarios where you need to route instance communications through a proxy server for security, compliance, or network routing reasons.

Practical examples include:

  • Enabling a proxy on an instance before sending messages to ensure traffic goes through a controlled gateway.
  • Disabling or verifying proxy settings to troubleshoot connectivity issues or confirm configuration.

Properties

Name Meaning
Nombre De La Instancia The name of the instance that will send the message.
Qué Desea Hacer Choose between "Definir Proxy" (set/enable proxy) or "Verificar Proxy" (check proxy status).
Activar Proxy Boolean to enable or disable proxy integration (only when setting proxy).
Protocolo Del Proxy Protocol used by the proxy: HTTP or HTTPS (only when setting proxy).
Host Del Proxy Hostname or IP address of the proxy server (only when setting proxy).
Puerto Del Proxy Port number of the proxy server (only when setting proxy).
Usuario Del Proxy Username for authenticating with the proxy server (only when setting proxy).
Contraseña Del Proxy Password for authenticating with the proxy server (only when setting proxy).

Output

The node outputs a JSON array containing the result of the proxy operation performed:

  • For Definir Proxy (setProxy), the output typically confirms whether the proxy was successfully set or disabled on the instance.
  • For Verificar Proxy (findProxy), the output provides the current proxy status and configuration details of the instance.

No binary data output is indicated.

Dependencies

  • Requires an API key credential to authenticate with the Wazend API.
  • The node uses the base URL https://docs.wazend.net/wazend for API requests.
  • Proper network access to the Wazend API endpoint is necessary.

Troubleshooting

  • Common Issues:

    • Incorrect instance name may cause the API to fail to find the target instance.
    • Invalid proxy host, port, username, or password can lead to authentication or connection errors.
    • Choosing the wrong operation option might result in unexpected behavior or errors.

  • Error Messages:

    • "Operação não suportada." indicates the selected operation is not supported for the resource; verify the chosen operation matches the node capabilities.
    • Network or authentication errors from the API should be checked by validating credentials and proxy parameters.

Links and References

Discussion