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 social media content. It allows users to report and request removal of harmful or infringing content hosted on various social media platforms. Typical use cases include reporting phishing attempts, malware distribution, brand infringement, or data leaks found on social media posts or profiles.

For example, a company noticing a phishing link impersonating their brand on Twitter can use this node to submit a takedown request directly to SOCRadar, specifying the platform, URL, and type of violation. This automates and streamlines the process of protecting brand reputation and user safety across multiple social media channels.

Properties

Name Meaning
Company ID The unique identifier of the company submitting the takedown request.
Social Media Platform The social media platform hosting the content. Options: Facebook, Instagram, Twitter, LinkedIn, YouTube, TikTok, Other.
URL The direct URL of the social media content to be taken down.
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: Additional information about the takedown.
- Tags: Comma-separated tags associated with the request.

Output

The node outputs JSON data representing the response from the SOCRadar API after attempting to create the takedown request. This typically includes confirmation details such as request ID, status, and any messages returned by the API.

If an error occurs during the request, the output JSON will contain error information including the error message and any additional details provided by the API.

No binary data is produced by this node.

Dependencies

  • Requires an active SOCRadar API key credential configured in n8n.
  • Network access to the SOCRadar API endpoint.
  • Proper configuration of the API base URL and authentication headers handled internally by the node.

Troubleshooting

  • Common Issues:

    • Invalid or missing API key credential will cause authentication failures.
    • Incorrect or malformed URLs may result in API errors or failed takedown submissions.
    • Unsupported social media platform values could lead to rejected requests.
    • Missing required fields like Company ID or URL will prevent the request from being sent.

  • 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 will output error details per item instead of stopping execution.
    • Common resolution steps include verifying credentials, ensuring all required parameters are correctly set, and checking the validity of the URL and platform selection.

Links and References

Discussion