Short answer: You can map site urls in Firecrawl by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Firecrawl Map Site URLs 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 to map. |
Filter Term search | string | Optional | Only return links whose URL or title contains this term. |
Limit limit | number | Optional | Maximum number of links to return. |
Include Subdomains include_subdomains | boolean | Optional | Follow subdomains of the given URL (e.g. blog.example.com when mapping example.com). |
{"url": "e.g. https://example.com","search": "e.g. blog","limit": "{{trigger.limit}}","include_subdomains": "{{trigger.include_subdomains}}"}
{"links": [{"url": "https://example.com/page1","title": "Page 1","description": "A description of page 1."},{"url": "https://example.com/page2","title": "Page 2","description": "A description of page 2."}],"success": true}
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.