crawl action type is navigation-first: start from known URLs (or URLs produced by an earlier step) and follow links within configured depth and breadth limits. Use it when discovery needs systematic expansion of a site or subgraph, not only a single hop into a fixed list of pages.
Examples use
TITAN_API_URL and TITAN_TOKEN. Tab titles match other integration pages. Rust: ureq + serde_json.When to use crawl
- You know entry URLs but not every target page in advance.
- Layout changes often, but internal linking is stable enough to traverse.
- You will hand off URLs to
scrapefor schema-shaped extraction, or combine crawl with search upstream.
Inputs and wiring
static_urls— crawl starts from URLs on the task.previous_step— crawl consumes URLs emitted bysearchor another step.task_url_inventory— crawl is driven from the URL inventory when your Titan environment supports that flow.
limits (depth, max pages, domain rules—whatever your template and script require) so runs stay bounded and predictable.
Single-action example (POST /api/v1/tasks)
Field names under limits are template-specific; align them with the script you bind.
- cURL
- Go
- TypeScript
- Python
- Rust
Chained example (crawl → scrape)
In anexecution_plan, keep each step self-contained. Crawl discovers URLs; scrape reads them into records:
Run
- cURL
- Go
- TypeScript
- Python
- Rust
Related topics
- Action types overview
- Search and Scrape
- Datasets and media for how outputs surface after runs