SOCRadar icon

SOCRadar

Comprehensive SOCRadar API integration
Join our community

Actions21

Overview

This node integrates with the SOCRadar API to create takedown requests specifically for domains under a company. The "Create Domain Takedown" operation allows users to report malicious or infringing domains such as phishing sites, malware hosts, brand infringement cases, or data leaks. This is useful in cybersecurity workflows where automated reporting and mitigation of harmful domains are needed.

Typical use cases include:

  • Automatically submitting takedown requests when suspicious domains are detected.
  • Managing domain-related threat intelligence by prioritizing takedown actions.
  • Enriching security incident response processes with direct API-driven takedown submissions.

Properties

Name Meaning
Company ID The unique identifier of the company for which the takedown request is being created.
Domain The specific domain name that the takedown request targets.
Takedown Type The category of the takedown request. Options: Phishing, Malware, Brand Infringement, Data Leak.
Priority The urgency level of the takedown request. Options: Low, Medium, High, Critical.
Additional Fields Optional extra details including:
- Description: Further information about the takedown.
- Tags: Comma-separated tags associated with the request.

Output

The node outputs JSON data representing the result of the takedown request creation. This typically includes confirmation details from the SOCRadar API such as request status, identifiers, and any metadata returned by the service.

No binary data output is involved in this operation.

Dependencies

  • Requires an active SOCRadar API key credential configured in n8n.
  • Network access to the SOCRadar API endpoint.
  • Proper configuration of the node with valid company ID and domain information.

Troubleshooting

  • Common Issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Incorrect or missing required properties (e.g., company ID, domain) will result in validation errors.
    • Network connectivity issues can prevent successful API calls.

  • Error Messages:

    • Errors returned from the SOCRadar API are captured and included in the output JSON under error and details.
    • If the node is set to continue on failure, it returns error details per item instead of stopping execution.

  • Resolution Tips:

    • Verify API key validity and permissions.
    • Ensure all required fields are correctly filled.
    • Check network connectivity and firewall settings.
    • Use the additional error details provided to diagnose API-specific issues.

Links and References

Discussion