Build an HTTP extraction
writ_create_http_extractionCreates or revises an advanced browserless HTTP extraction from plain language and real browser-network evidence (a browser experiment or capture_network). For: what one simple request or a named auth/function graph cannot express (request loops, GraphQL descriptor discovery, recursive JSON, cross-page dedupe, sorting, cursor pagination); ordinary login/bootstrap/data chains are writ_browser_compose define_function with is_auth/order/typed response_extractions. Generates a universal api_call.config.flow; site behavior stays inside the workflow. apply=false returns the draft and its validation; apply=true writes a valid draft. It is ready to expose once writ_diagnose_http_workflow shows a run with engine=http and records. Requests are flow steps (no fetch in evaluate_js); Writ-only controls never reach the site.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| goal | Yes | Exact inputs, output fields, filters, ordering and pagination behavior wanted. | |
| apply | No | false (default) returns a reviewable draft; true writes a valid draft to the workflow. | |
| workflow | No | Existing workflow name (or workflow_id). | |
| step_index | No | api_call step to replace; defaults to the first, or appends one. | |
| workflow_id | No | ||
| requirements | No | Extra mapping, dedupe, filtering or cursor requirements. | |
| desired_inputs | No | Caller parameters such as query, min_price, max_price, limit and cursor. | |
| request_samples | No | Relevant calls returned by writ_browser_network/capture_network, including representative response bodies when available. | |
| response_sample | No | Optional representative JSON/HTML response when it is not in request_samples. |