Outscraper icon

Outscraper

Interact with Outscraper API

Actions49

Overview

This node integrates with the Outscraper API to fetch reviews from the Apple App Store. It allows users to retrieve detailed user feedback for any app by specifying its direct link or ID. This is particularly useful for market researchers, app developers, and marketers who want to analyze user sentiment, monitor app reputation, or gather competitive intelligence.

Practical examples include:

  • Extracting the latest 50 reviews of a messaging app to understand recent user issues.
  • Sorting reviews by most helpful to identify key feature requests or common complaints.
  • Using asynchronous requests with webhooks to handle large data retrieval without blocking workflows.

Properties

Name Meaning
Query Direct links or IDs of any AppStore app (e.g., https://apps.apple.com/us/app/telegram-messenger/id686449807 or id686449807). This identifies the app whose reviews are fetched.
Limit Maximum number of review results to return. Minimum value is 1. Default is 50.
Sort Sort order for reviews. Options: "Most Helpful" or "Most Recent".
Cutoff Oldest timestamp value for items; overrides sort to newest first. Used to filter out older reviews.
Async Request Boolean flag indicating whether to make an asynchronous request. Useful for long-running tasks.
Webhook URL to which Outscraper will send a POST request once the asynchronous task is finished.
Additional Fields Collection of optional parameters:
- Fields: Specific fields to return (comma-separated).
- UI: Whether to execute the request as a UI task (boolean).

Output

The node outputs JSON data containing the requested App Store reviews. Each item in the output typically includes details such as review text, rating, date, reviewer information, and other metadata depending on the selected fields.

If binary data were supported (not indicated here), it would represent attachments or media related to reviews, but this node focuses on JSON review data only.

Dependencies

  • Requires an active Outscraper API key credential configured in n8n.
  • The base URL for the API is configurable via credentials.
  • For asynchronous requests, a publicly accessible webhook URL must be provided to receive callbacks when the task completes.

Troubleshooting

  • Common Issues:

    • Invalid or missing app ID/link in the Query property may result in no data or errors.
    • Exceeding the API rate limits or quota can cause request failures.
    • Incorrect webhook URL or network issues can prevent receiving asynchronous task completion notifications.
  • Error Messages:

    • "Invalid API key" — Check that the API key credential is correctly set up.
    • "App not found" — Verify the app ID or URL is correct and publicly accessible.
    • "Request timeout" — Consider enabling asynchronous mode for large queries or check network connectivity.
    • "Webhook delivery failed" — Ensure the webhook URL is reachable and accepts POST requests.

Links and References

Discussion