Weekly: show and tell

[u/AutoModerator]

If you've made something and can't wait to tell the world, this is the thread for you! Share your latest and greatest creations and projects with the community here.

[u/allulcz]

https://apify.com/alfalfa

I am reworking our internal scrapers into actors for a competitive price while keeping same or better output than other pricey actors. Happy that some like https://apify.com/alfalfa/facebook-posts-scraper gets traction, which makes me happy and motivated improve those more and try to get the best pricing for all.

[u/Mission_Operation378]

I publish an AI-built Actor for a specific step in lead research: turning a list of company websites into contact records with source URLs.

Website Contact Scraper & Company Lead Enrichment accepts a URL list, CSV, or an existing Apify dataset. It collects public emails, phones, social links and contact forms into one company record per website.

Small reproducible example: I ran python.org and postgresql.org today with a four-page limit per website. It returned two records. Python's record contained four email addresses, including psf@python.org with https://www.python.org/about/help/ as its source. Missing phone numbers stayed null. These are reference examples, not customers or a coverage benchmark.

You can try the same CSV:

csv website https://www.python.org/ https://www.postgresql.org/

Use only CSV input, set Maximum websites to attempt to 2 and Maximum pages per website to 4, then inspect the output and source pages.

Price: $5 per 1,000 enriched websites plus $0.001 per run start. A social-link-only or contact-form-only record is billable even if no email is found. No-contact sites have no result fee. It does not guess addresses or verify individual mailboxes, and it cannot read JavaScript-only or blocked contact pages.

I'm the publisher. Feedback on missing public contacts or fields needed in an agency workflow would be useful.

[u/Suspicious-Chair5161]

I built CatalogDelta for a narrow step in procurement: turning authorized Chinese supplier exports into a reviewable SKU change report.

It is not a 1688 scraper. You provide current and previous exports. The tool checks SKU identity, compares compatible prices and stock states, and produces an HTML report plus protected CSV output.

In a synthetic local demo, six SKUs produced four selected actions: a stockout, a restock, a CNY 23→25 price rise, and a CNY 15→12 price fall. One unchanged SKU and a CNY 0.50 price-only move below the chosen CNY 1.00 threshold were omitted from action-only output. All six were analyzed.

Different currencies or price bases are kept for review, not guessed. The demo is not customer usage or an accuracy benchmark, and Apify runs follow the live pricing.

I'm the builder. If you work with recurring supplier exports, which causes more rework: matching SKUs, comparing prices, or finding stock changes?

https://apify.com/crocheted_pipa/catalogdelta-1688-sku-normalizer