Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node updates a Discovery Setting in the Connect Secure system via its API. It allows users to modify specific configuration parameters related to network discovery, such as ports to ignore, scheduling scans, and exclusion status. This is useful for automating network management tasks, ensuring that discovery settings remain up-to-date without manual intervention.

Practical examples include:

  • Automatically excluding certain devices or IP ranges from network scans.
  • Scheduling scans to be deferred or enabled based on dynamic conditions.
  • Customizing port scanning behavior by ignoring specified ports.

Properties

Name Meaning
X USER ID The user identifier required for authentication or tracking of the request.
Data JSON object containing the discovery setting details to update. Includes:
- ignore_ports: Array of ports to exclude from scanning.
- scan_later: Boolean flag indicating whether to defer scanning.
- is_excluded: Boolean flag indicating if the target is excluded from discovery.
Id Numeric identifier of the specific discovery setting to update.

Output

The node outputs JSON data representing the response from the Connect Secure API after updating the discovery setting. This typically includes confirmation of the updated fields or the full updated resource representation.

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

  • Common issues:

    • Missing or invalid user ID header (X USER ID) may cause authentication or authorization failures.
    • Incorrect or malformed JSON in the Data property can lead to request rejection.
    • Providing an invalid or non-existent Id will result in errors indicating the resource was not found.
  • Error messages:

    • Authentication errors usually indicate missing or incorrect API credentials or user ID.
    • Validation errors often point to improperly formatted JSON or missing required fields.
    • Not found errors suggest the specified discovery setting ID does not exist.

To resolve these, ensure all required properties are correctly set, the API credentials are valid, and the target discovery setting exists.

Links and References

  • Connect Secure API documentation (refer to your organization's API docs for detailed schema and examples).
  • n8n documentation on creating and using HTTP Request nodes for custom API integrations.

Discussion