Short answer: You can scrapingbee scrape url in ScrapingBee by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the ScrapingBee ScrapingBee Scrape URL action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
URL url | string | Required | URL (required) |
Render JS render_js | options | Optional | Render JS. Options: Yes, No |
Premium Proxy premium_proxy | options | Optional | Premium Proxy. Options: Yes, No |
Country Code country_code | string | Optional | us |
{"url": "e.g. https://example.com/path","render_js": "{{trigger.render_js}}","premium_proxy": "{{trigger.premium_proxy}}","country_code": "us"}
"<html>...</html>"
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.