Connect Secure icon

Connect Secure

Consume Connect Secure API

Actions222

Overview

This node allows you to create a new Asset by sending structured data to an external API. It is useful in scenarios where you need to programmatically register or add asset information into a system that tracks devices, software, or other resources. For example, you might use this node to automate the onboarding of new hardware assets into an inventory management platform or to update asset details as part of a larger workflow.

Properties

Name Meaning
X USER ID The user identifier required for authentication or tracking purposes. This value is sent as a custom HTTP header X-USER-ID.
Data JSON-formatted data representing the asset details to be created. This includes fields such as OS patches, SNMP info, firewall status, unique IDs, status flags, discovered protocols, scan status, and required patches.

The Data property expects a JSON string which will be parsed and sent as the request body. A typical default structure looks like:

{
  "os_patches": "[]",
  "snmp_info": "[]",
  "is_firewall": false,
  "unique_id": "[]",
  "status": true,
  "is_deprecated": false,
  "discovered_protocols": "[]",
  "scan_status": true,
  "install_required_patches": "[]"
}

Output

The node outputs the response from the API call in the json field of the output item. This typically contains the newly created asset's details or confirmation of creation. The exact structure depends on the external API's response format.

No binary data output is indicated.

Dependencies

  • Requires an API key credential for authenticating with the external Connect Secure API.
  • The node uses the X-USER-ID header for user identification, which must be provided.
  • The node depends on the external Connect Secure API being accessible and properly configured.

Troubleshooting

  • Invalid or missing X USER ID: The API may reject requests without a valid user ID header. Ensure this property is set correctly.
  • Malformed JSON in Data: Since the Data property expects a JSON string, invalid JSON will cause parsing errors. Validate JSON syntax before running the node.
  • API connectivity issues: Network problems or incorrect API credentials can cause failures. Verify API endpoint accessibility and credential validity.
  • Unexpected API responses: If the API returns errors, check the response message for clues. Common issues include permission errors, missing required fields, or invalid data formats.

Links and References

Discussion