FAQ

A hosted scrape & monitor platform. You design a workflow in the browser (URL gen → scrape → store → notify); we run it in the cloud on your schedule — no crawlers or Chrome extension to maintain.

Create a free account, new workflow, add a scrape node, paste a public sample URL, Fetch fields, tick columns, then Run once. Or use homepage quick analyze, or follow Getting started.

No. You design in the browser; execution is in the cloud. Active workflows with an interval keep running even when your laptop is closed.

No. Describe fields in plain language (e.g. title, price, product url). The scrape node discovers candidate columns; you tick what to keep. Those rules reuse on later runs.

Collect usually means write every run into a dataset. Monitor is the same graph plus a schedule and a notify node for new rows or field changes. Same nodes — different interval and notify when.

Open the right-panel AI chat on a workflow to analyze a page or reshape the graph in plain language. Changes appear on the canvas; click Save to persist. Requires AI_API_KEY.

Yes. Scrape the list (keep a link/url column), connect a detail scrape, set input_field to that column. Detail rows merge list fields when matching works. Detail bills one credit per requested URL.

The engine works on publicly reachable pages. Login walls, aggressive bot blocks, or CAPTCHAs often fail. Try a simpler public list URL or rewrite the requirement. Open the run’s node error for details.

URL generator: max 500 per node. Each scrape defaults to 20 URLs per run — raise limit if needed. If you generate many pages, raise the downstream scrape.limit too.

Set interval_minutes on the workflow: 1440 ≈ daily, 60 ≈ hourly (plan permitting). Empty means manual only. Run manually until fields look right, then set active + interval.

when=new emails on new key rows; when=field_change watches fields like price. Use test / dry-run to check triggers. Default destination is your account email.

Store upserts by key_fields (often url/link). Set a stable business key (product URL) so reruns update prices instead of duplicating rows.

No. Credits are spent only when a run produces rows. Pause skips the scheduler; you can still run manually.

One credit = one webpage request by scrape nodes. Free is 20/month; Starter 2,000, Pro 5,000, Business 15,000. Yearly plans grant 12× monthly credits upfront.

Yes. Free includes 20 credits/month with no card. Paid plans go to 15,000 credits/month; yearly billing is ~20% off with 12× credits upfront. See Pricing.

Only when scrape nodes actually request pages during a run. Saving the canvas, URL gen, store, and notify do not spend credits. Out of credits → HTTP 402; upgrade or wait for the next period.

One credit equals one webpage request by scrape nodes. Three list pages = 3 credits; ten detail URLs = 10. Output row count does not matter.

New runs return HTTP 402 until the next period or you upgrade. Existing datasets stay available.

Yes. Yearly plans receive 12× monthly credits upfront when activated.

Your data stays. Remaining credits follow the new plan after the current period ends.

Manual plans can be reversed by an admin before the period ends. Card billing will follow Stripe policy when enabled.

Yes. Create a key starting with hulu_ in the console and call /api/v1 with Authorization: Bearer. Session cookies from website login are not accepted on the API.

Console → Datasets: browse rows, export CSV or JSON (row cap applies). Or API: GET /api/v1/datasets/{id}/rows or …/export.

You choose the URLs. Collect only pages you are allowed to use, and follow target-site terms and law. We do not bypass logins or CAPTCHAs. For a DPA or enterprise needs, use the contact form.

Not today. The product targets public pages. Login, session, or CAPTCHA-gated sites are out of scope. Use public URLs you are allowed to collect.