Publisher · 4 actors

datataskflow on the Apify Store

datataskflow publishes 4 actors on the Apify Store, used by 4 people in the last 30 days. Oldest actor is 22d old. Prices, reliability and maintenance below come from our daily census of the public store catalog.

Claim this publisherIs this your catalogue? Claiming is free, and its full history is yours forever.
Last 7 dayson this catalogue

…and 5 more changes this week. Follow datataskflow — every change by email each morning

By monthly users#2,238↑ 405of 4,120 publishers · 4 users in 30 days
By catalogue size#1,857↑ 499of 4,120 publishers · 4 actors listed
By users all time#2,797↑ 547of 4,120 publishers · 6 users since they began
Needs a build0 of 44 fresh · 0 aging · stale = no build in 180 days
Carry half the users2 of 4top 3 hold 75% · 25% on the largest

Places are over the 4,120 publishers listed today; the week’s move is measured against the 3,645 also listed on 17 Oct, so nobody falls because the store grew around them.

What they build4 actors in the catalogue
Platforms targeted
Ashby1
Greenhouse1
Lever1
Recruitee1
SmartRecruiters1
Google Trends1

2 of 4 target no particular site

Biggest actors, monthly users
whois-domain-lookup-scraper25%
career-site-job-scraper25%
website-tech-stack-scraper25%
google-trends-scraper25%

share of this publisher’s 4 monthly users

6platforms targeted
4.1 a monthnew actors, last 30 days
Oct 2026first actor still listed
3dsince their newest actor

datataskflow spreads 4 actors across 6 platforms, most of all Ashby (1). They have created 4.1 a month over the last 30 days.

How this is counted

Platforms come from our own classification of each actor’s listing, and an actor can target several — so these counts overlap and add up to more than the catalogue. Dates are the store’s own creation timestamp for each actor, which means the chart shows the actors still listed today, grouped by when they were made: a publisher who built forty last year and has since removed thirty shows ten. Shares are of this publisher’s own monthly users, from the same daily census as the table below.

Monthly userssummed across this catalogue
4↑ 2over 22 readings
Runs / daymatched per actor
12↑ 6over 21 readings
Runs / 30drolling window, summed
48↑ 48over 22 readings
Actorsin the census that day
4↑ 2over 22 readings

Runs per day is each actor's own step in its lifetime run counter, added up over the actors present on both days — an actor joining this catalogue moves the actor count, never the runs line. Last 30 days; the full history is in the app.

Build activitylast 60 days
0builds published
0/60days with a build
100%of the catalogue touched in 30 days
Last touched
2–7d2
8–30d2

No build from datataskflow in the last 60 days.

How this is counted

A build is counted from the store's own build counter, read once a day, so a cell is an exact count and an empty cell is a day nobody shipped. Shading runs against this catalogue's busiest day, so it compares days here — not catalogues. “Touched” is broader than a build: it is the last change the store saw of any kind, on a rolling re-fetch, so it can lag a build by days. Per-actor history is in the app.

Sort
#ActorGradePrice / 1kUsers /30dSuccessRatingAgeFresh
1—EVT$1.75 /1k domain-lookup12 total——3dfresh
2—EVT$2.25 /1k job11 total——22dfresh
3—EVT$1.00 /1k website-scan12 total——7dfresh
4—EVT$1.50 /1k keyword11 total——22dfresh
4 actors, sorted by monthly users · * prices normalized per 1,000 units Open in search with filters →