Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node allows users to create a new Discovery Setting in the Connect Secure system via its API. Discovery Settings typically control how network discovery scans behave, such as which ports to ignore or whether certain hosts should be excluded from scanning. This node is useful for automating the configuration of network discovery parameters, enabling dynamic adjustment of scan settings based on external triggers or workflows.

Practical examples include:

  • Automatically setting up discovery exclusions for newly added devices.
  • Scheduling scans with specific port ignores or flags.
  • Integrating discovery setting creation into broader network management automation.

Properties

Name Meaning
X USER ID User Id header value required for authentication or identification in the API request.
Data JSON object representing the discovery setting details. It includes:
- ignore_ports: Array of ports to ignore during scanning (e.g., [] means none).
- scan_later: Boolean flag indicating if the scan should be deferred.
- is_excluded: Boolean flag indicating if the target is excluded from discovery.

Output

The node outputs the JSON response returned by the Connect Secure API after creating the discovery setting. This typically contains confirmation details about the created setting, including any identifiers or status messages.

No binary data output is involved.

Dependencies

  • Requires an API key credential for authenticating with the Connect Secure API.
  • The node depends on the Connect Secure API being accessible and properly configured.
  • No additional environment variables are explicitly required beyond the API credential.

Troubleshooting

  • Missing or invalid X USER ID: The API requires the X USER ID header; ensure it is provided and correct.
  • Malformed JSON in Data property: The data field must be valid JSON. Errors parsing this will cause the request to fail.
  • API connectivity issues: Network problems or incorrect API credentials will prevent successful creation.
  • Permission errors: Insufficient permissions for the user ID may result in authorization failures.

To resolve these:

  • Double-check the X USER ID input.
  • Validate the JSON structure in the Data property before execution.
  • Verify API credentials and network access.
  • Confirm user permissions with the Connect Secure administrator.

Links and References

Discussion