Short answer: You can run firecrawl agent in Firecrawl by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Firecrawl Run Firecrawl Agent 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 |
|---|---|---|---|
Starting URL url | string | Optional | Optional. If blank, the agent runs in discovery mode and decides where to look based on the task + schema. Provide a URL when you want the agent to anchor to a specific page. |
Agent Task prompt | string | Required | Natural-language instruction for the agent. Be specific about what to do and what to extract. Examples: "Click the Pricing link and extract every plan name with its monthly price." or "Return the title and points of the top 3 stories from the front page." |
Agent Model model | options | Optional | Which Spark model to use. Mini is the Firecrawl API default and works well for most tasks; switch to Pro only if Mini repeatedly fails on a specific page. |
Output Schema schema | json_schema | Optional | Define the shape of `data` you want the agent to return. Leave empty to get prose output instead of structured JSON. |
{"url": "e.g. https://news.ycombinator.com","prompt": "e.g. Find the company's contact email on the About or Contact page","model": "{{trigger.model}}","schema": "{{trigger.schema}}"}
{"data": [{"title": "I Moved My Digital Stack to Europe","points": 52},{"title": "Deterministic Fully-Static Whole-Binary Translation","points": 218},{"title": "New stainless steel for hydrogen production","points": 97}],"model": "spark-1-pro","status": "completed","success": true,"expiresAt": "2026-05-14T12:58:46.741Z","creditsUsed": 0}
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.