SOCRadar icon

SOCRadar

Comprehensive SOCRadar API integration

Overview

The node integrates with the SOCRadar API to manage digital footprint assets for companies. Specifically, the "Add Asset" operation under the "Digital Footprint" resource allows users to add various types of digital assets related to a company’s online presence and infrastructure.

This node is beneficial in scenarios where organizations want to programmatically track and enrich their digital footprint by adding assets such as domains, IP addresses, websites, SSL certificates, social accounts, and more. For example, security teams can use it to maintain an up-to-date inventory of internet-facing assets to monitor for vulnerabilities or suspicious activity.

Practical examples:

  • Adding a new domain or IP address associated with a company to the digital footprint database.
  • Registering a cloud bucket or source code repository as part of the company’s monitored assets.
  • Tracking mobile applications or social media accounts linked to the company.

Properties

Name Meaning
Company ID The unique identifier of the company to which the asset will be added.
Asset Type The category/type of the asset being added. Options include: Domain, IP Address, Website, Login Page, DNS Record, SSL Certificate, IP Block, Mobile Application, Technology, Cloud Buckets, Social Accounts, Source Code Repo.
Asset Name The name or identifier of the asset to add (e.g., domain name, IP address string).

Output

The node outputs JSON data representing the result of the "Add Asset" operation. This typically includes confirmation details about the newly added asset, such as its ID, status, or any metadata returned by the SOCRadar API.

If an error occurs during the operation, the output JSON will contain an error field with the error message and possibly additional details from the API response.

The node does not output binary data.

Dependencies

  • Requires an active SOCRadar API key credential configured in n8n.
  • The node makes HTTP requests to the SOCRadar API base URL using the provided API key.
  • No other external dependencies are indicated.

Troubleshooting

  • Common issues:

    • Invalid or missing API key credential will cause authentication failures.
    • Providing an incorrect Company ID or Asset Type may result in API errors.
    • Network connectivity problems can prevent successful API calls.
  • Error messages:

    • Errors returned from the SOCRadar API are captured and included in the output JSON under an error field.
    • If the node is set to continue on failure, it will output the error details without stopping the workflow.
    • Typical error messages might include authorization failures, invalid parameters, or rate limiting notices.
  • Resolution tips:

    • Verify that the API key credential is correctly set up and has necessary permissions.
    • Double-check the Company ID and Asset Type values for correctness.
    • Ensure network access to the SOCRadar API endpoint.
    • Enable "Continue On Fail" in the node settings to handle errors gracefully during batch operations.

Links and References

Discussion