Instagram Hashtag Scraper avatar
Instagram Hashtag Scraper

Pricing

$2.30 / 1,000 results

Go to Store
Instagram Hashtag Scraper

Instagram Hashtag Scraper

Developed by

Apify

Apify

Maintained by Apify

Scrape Instagram hashtags data. Just add one or more hashtags and extract posts, images, URLs, comments, likes, users, locations, timestamps, and more. Export scraped datasets, run the scraper via API, schedule and monitor runs or integrate with other tools.

4.5 (22)

Pricing

$2.30 / 1,000 results

248

Total users

24K

Monthly users

1.9K

Runs succeeded

>99%

Issues response

5.4 days

Last modified

2 days ago

KI

Suggestions & ideas

Closed

kirollos opened this issue
a year ago

is it possible to

  • put a button to import txt file with the hashtags I want to scrap and made a button to update it either by uploading or from google drive -put a field that i want to export before i run the task and by that i can save my usage and time -put conditions to filter my search based on a specific hashtag combination like give me the posts that has that hashtag in condition it come with another hashtag #1st #2nd and don't collect the posts that has just one of them
KI

kirollos

a year ago

these fields should be in the section before running the task also should have a save button so i don't have to choose them every time i run the task

alexey avatar

Hi!

Its related to Console UI, actor developers can not change it, since there is no templating or customization for most of the above by actor code. Web interface its the same across all actors.

If you need your own approach please check API or consider integration with third party tools, i.e. Zapier

I´m going to close the issue now, but if there would be anything else we could help with, please let us know.

zuzka avatar

Hey, just to let you know we shared your feedback with the team. I wanted to make a note about point 3 - choosing the fields before scraping - we almost always do it when it influences the price of the run, so if the Actor needs to make an extra request, you can usually opt in/out. But in this case, the Actor gets all this information in one request (per post) so the only difference in price would be the storage, which is marginal in the price of the run, so you wouldnt really see any difference.