Apify Reviews & Product Details

Easy to set up actors, flexible automation tools, and good integration options for scraping workflows. Review collected by and hosted on G2.com.

Our experience with Apify’s Twitter scraper started positively, but over time it became extremely disappointing and costly due to multiple issues that directly affected reliability and budget control.

1. Parameters not working as expected

Many of the parameters provided by the actor did not behave consistently. Even when we configured limits such as maximum items to fetch, the scraper did not always respect them. This made it very difficult to rely on the actor in a production workflow where predictable behavior is critical.

2. Unnecessary fetching that wasted our budget

On several occasions the scraper fetched thousands of tweets even though strict limits were configured. These runs consumed a large amount of resources and unexpectedly increased our costs. What made this worse was that these fetches were not intentionally triggered by us, yet the platform still charged for them. When we raised the issue, there was no meaningful resolution or refund, even though the behavior clearly went beyond the configured limits.

3. Fetching outdated tweets instead of recent ones

Another recurring issue was that the scraper frequently returned old tweets instead of the latest ones, even when using options intended to retrieve the most recent results. For time-sensitive workflows this makes the data unreliable. We often saw situations where tweets from the previous day appeared while tweets posted within the last hour were missing entirely.

4. Uncertain and inconsistent scraper behavior

The overall behavior of the Twitter scraper felt unpredictable. Identical configurations would sometimes produce completely different results between runs. Some runs would miss relevant tweets, while others would return irrelevant or outdated data. This level of inconsistency makes it difficult to trust the tool for automated systems.

While Apify provides a capable platform and a developer-friendly interface, the lack of strict control over limits, unreliable scraping results, and poor cost safeguards created serious operational issues for us. For any system that depends on predictable data collection and controlled spending, these problems can become very costly very quickly.

Until stronger safeguards, clearer parameter behavior, and better cost protection mechanisms are implemented, it is difficult to recommend relying on the Twitter scraper for production-critical workflows. Review collected by and hosted on G2.com.

What I like most about Apify is how flexible and reliable it is for web scraping and automation. The platform makes it easy to run ready-made Actors from the Apify Store, and at the same time, it gives you full control if you want to build custom scrapers.

I also appreciate how everything is cloud-based — scheduling, monitoring, API access, and proxy management are all handled in one place. The dashboard is clean, logs are detailed, and it’s easy to track runs and debug when needed. Once you get used to it, it becomes a very powerful tool. Review collected by and hosted on G2.com.

Nothing to dislike for me. It's an gamechanger for my use case. I automated a lot of works using Apify. Review collected by and hosted on G2.com.

The most helpful aspect of Apify is the combination of a powerful cloud infrastructure and the extensive Actor Store. It effectively handles complex anti-scraping measures like browser fingerprinting and proxy rotation automatically. Being able to deploy pre-built scrapers for major sites in minutes, rather than writing custom code for weeks, is a massive upside for our productivity. Review collected by and hosted on G2.com.

The credit-based pricing system can be somewhat difficult to predict for complex, large-scale crawls, which makes budgeting a bit of a challenge. Additionally, while the platform is incredibly powerful, the sheer number of features creates a steep learning curve for non-technical team members who just need to download a simple dataset. Review collected by and hosted on G2.com.

What I like best about Apify is how quickly I can go from idea to actual data. For things like Google Maps scraping, I don’t need to build a crawler from scratch, I can just use an existing actor, set my search keywords and locations, and start getting results in minutes.

The platform handles things like proxies, browser automation, and blocking much better than most DIY setups. I also like that the data comes out clean in JSON, CSV, or Excel, which makes it easy to use in my own tools and dashboards. Overall it saves a lot of engineering time compared to running and maintaining my own scrapers. Review collected by and hosted on G2.com.

One thing I don’t like is that the pricing can become expensive when you run scrapers at scale, especially for data-heavy sources like Google Maps where a lot of proxy and compute usage is required. If you’re running large jobs or frequent crawls, the costs add up quickly.

I also found that some actors can fail or return partial data when Google changes something, so you sometimes have to rerun jobs or tweak settings. It’s not a deal breaker, but it does mean you still need to monitor runs instead of treating it as completely hands-off. Review collected by and hosted on G2.com.

I love Apify’s interface and usability, which sets it apart from other platforms that tend to be difficult to navigate. This user-friendly design made it easy for me to get accustomed to the software right from the start. Apify has greatly simplified my ability to access lead data for my outbound outreach campaigns, specifically when scraping LinkedIn profile data. Its ease of use is invaluable, especially compared to my previous experience with other products like ScrapeNinja, which didn't perform as effectively. I also feel confident in recommending Apify to others based on its strong points, and I rate it highly due to these features. Review collected by and hosted on G2.com.

I find the API side of Apify could be improved in terms of ease of use. Integrating actors with some automation platforms like n8n can get complicated at times. Additionally, the API documentation could be simplified to make it easier for users to understand and implement. Review collected by and hosted on G2.com.

Apify provides an excellent balance between flexibility and infrastructure. I can build custom Actors for complex data extraction without worrying about servers, scaling, proxy rotation, retries, or failures. The SDK, scheduling, webhooks, datasets, and API access make it easy to go from idea to production very fast. It saves a huge amount of development and maintenance time. Review collected by and hosted on G2.com.

Apify offers multiple pricing plans and usage based components, which can sometimes feel a bit complex or confusing at first. For new users, understanding how different plans, compute units, and add on services interact may require extra time. Clearer upfront guidance or simpler pricing tiers would help reduce this learning curve. Review collected by and hosted on G2.com.

- ready-to use templates or services

- faster delivery

- the ability to publish SaaS or automation Actors (services) Review collected by and hosted on G2.com.

- the pricing docs / structure

- for developers: dynamic select options rather than static options in the json file

- for UX: there are inputs that depend on another input value and thus based on the input value we shall show only the relevant inputs, for example an input 1 is a select input that has 2 options (option 1 and option 2), based on it's value I shall show input 2 and input 5 if I select option 1, and I shall show input 3 and input 4 if I select option 2, what happens is that we display all the inputs (input 1, input 2, input 3, input 4, input 5) Review collected by and hosted on G2.com.

What I like best about Apify is how it combines power, flexibility, and reliability in one platform. The ready-made actors make it easy to get started quickly, while the option to build custom actors allows us to handle complex, real-world use cases. It handles dynamic websites extremely well, scales without infrastructure headaches, and fits seamlessly into our existing workflows—helping us move faster and focus on insights rather than manual data collection. Review collected by and hosted on G2.com.

What I dislike about Apify is that some advanced use cases come with a steeper learning curve, especially for non-technical users. Debugging failed runs can also take time, as logs are detailed but not always easy to interpret quickly. Additionally, at higher usage levels, cost predictability requires close monitoring, which means teams need to plan and optimize runs carefully. Review collected by and hosted on G2.com.

The sheer versatility of the platform is unmatched. I was able to build a sophisticated "Intelligence Engine" using Playwright and PDF parsing while staying within a 1GB RAM footprint. The "Bring Your Own Key" (BYOK) AI flexibility is a huge advantage, allowing me to build scalable tools without worrying about vendor lock-in or high compute costs. Review collected by and hosted on G2.com.

The learning curve for the metadata and input schemas is quite steep. The platform is very strict about naming conventions (like dataset names needing specific hyphenation) and mandatory description fields. While it ensures high-quality tools in the Store, it can be a bit frustrating for new developers during the first few builds. Review collected by and hosted on G2.com.

I’ve been using Apify mainly for YouTube Scraper and Instagram Scraper, and overall, the experience has been very positive. The platform is easy to use, cloud-based, and offers ready-made scrapers that save a lot of time. The Instagram Scraper works smoothly for pulling posts, hashtags, and comments, while the YouTube Scraper is great for extracting video data without much hassle. I also appreciate that Apify provides scalability, scheduling options, and integration with APIs, which makes automation feel effortless. Review collected by and hosted on G2.com.

There are a few things that could be better. Pricing can get expensive if you’re running large-scale scrapes, and sometimes the scrapers need tweaking when platforms change their structures. Review collected by and hosted on G2.com.