Outscraper icon

Outscraper

Interact with Outscraper API

Actions49

Overview

This node integrates with the Outscraper API to retrieve Twitter profile information based on user queries. It is designed to fetch detailed data about Twitter profiles by providing links or usernames. The node supports both synchronous and asynchronous requests, allowing users to either wait for immediate results or receive them via a webhook callback once processing completes.

Common scenarios where this node is beneficial:

  • Marketing teams wanting to gather public Twitter profile data for lead generation or audience analysis.
  • Social media analysts collecting profile details for sentiment or influence measurement.
  • Developers automating data collection from Twitter profiles without direct API access.

Practical example:

  • Inputting a Twitter username like outscraper or a full URL such as https://www.twitter.com/outscraper to retrieve profile details including follower count, bio, location, and other specified fields.

Properties

Name Meaning
Query Links to Twitter pages or usernames (e.g., https://www.twitter.com/outscraper, outscraper).
Async Request Whether to make an asynchronous request (true or false).
Webhook URL address to which Outscraper will send a POST request once the task is finished (callback URL).
Additional Fields Collection of optional parameters:
- Fields: Specific fields to return (comma-separated).
- UI: Whether to execute the request as a UI task (true or false).

Output

The node outputs JSON data containing the requested Twitter profile information. The structure typically includes profile details such as username, display name, bio, follower counts, and any additional fields specified in the input.

If the request is asynchronous, the output may initially contain task status or identifiers, with the final data delivered later to the provided webhook URL.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active Outscraper API key credential configured in n8n.
  • Network access to the Outscraper API endpoint.
  • For asynchronous requests, a publicly accessible webhook URL must be provided to receive callbacks.

Troubleshooting

  • Common issues:

    • Invalid or missing query parameter: Ensure the "Query" field is correctly filled with valid Twitter usernames or URLs.
    • Incorrect webhook URL: For async requests, verify that the webhook URL is reachable and correctly formatted.
    • API key errors: Confirm that the API key credential is valid and has sufficient permissions.

  • Error messages:

    • Authentication failures usually indicate invalid or expired API keys; reconfigure credentials.
    • Request timeouts or network errors suggest connectivity problems; check internet access and API availability.
    • Validation errors on fields may occur if unsupported or incorrectly formatted fields are requested; review the "Fields" input.

Links and References

Discussion