Turn a defined search or existing routine into a usable research table.
Copy a prompt into your agent with the oo Skill installed. Add your page links and source notes before running it.
Create a supported company search and collect its result pages.
/oo Clay: Read Clay’s search query reference and form a company query for [criteria]. Create the search, retain its search ID, and fetch results up to [maximum count] while more results remain. Make a table using the fields present and note whether the search ended because results ran out or a query limit was reached.
Process supplied records and separate successful and failed item results.
/oo Clay: Run Clay routine [routine ID] on these items [items with stable IDs and required fields]. Keep the routine run ID, check progress and read result pages using their cursor. Return successful output fields in a table keyed by item ID and list item errors separately, even if the overall run is complete.
Set up oo CLI and the oo Skill in your agent.
Install OOMOL →Connect with a Clay API key for your workspace.
Connect Clay →Use /oo with the pages to read, the changes to make, and where to save the result.
Connection Guide →Choose Your Agent
Search people and company data through Clay’s query tools, run existing routines on supplied items or a batch file, and retrieve results. Table and workflow-run queries also support inspection of existing workspace data.
Create a query-based search and retrieve successive results.
Run routines on items or JSONL batch files and inspect results.
Read table data (Enterprise capability) and workflow-run records with supplied queries.
Download a JSONL file, upload it to Clay, and start an asynchronous batch routine. Each line must contain id and inputs. The routine may perform arbitrary downstream mutations. Connector transfer limit: 2 GiB, five minutes each for download and upload; JSONL validation is performed by Clay.
Leina 
Wanta 
clay.run_routine_batch Get batch progress, a result download URL, or validation/processing failure details. Download result_url separately after completion and inspect individual item outcomes; results are not loaded into the action response.
clay.get_routine_batch_results Get the Clay user and workspace associated with the API key.
clay.get_me Get workspace credit balances without consuming credits.
clay.get_credit_balance Get the current Clay search query grammar and fields before creating a search.
clay.get_search_query_reference Create a stateful company or people search from a Clay query. Count-mode and jobs queries are unsupported.
clay.create_search Fetch the next page and advance a Clay search iterator. Do not retry blindly: each call advances the iterator.
clay.get_search_results Run a configured Clay routine on 1–100 items asynchronously. The routine may perform arbitrary downstream mutations; inspect its definition before running.
clay.run_routine Get routine progress or one page of completed results. Follow cursor until absent and check each item's status.
clay.get_routine_results Query known Clay tables on Enterprise plans. Concurrent updates can repeat rows; deduplicate by ID. Custom ordering and aggregation do not support cursor pagination.
clay.query_tables Get the workflow-run query grammar and supported fields (beta).
clay.get_workflow_run_query_reference Search or count workflow runs (beta). Results are eventually consistent; recently changed runs may be stale or absent.
clay.query_workflow_runs No matching tools.
Provide an accessible JSONL file URL and existing routine ID. Batch execution returns a run ID; check that run for progress, errors and a result file URL when complete.
Keep successful results and list failed item IDs with their errors. Overall completion means processing ended, not that every item succeeded.
The assistant can read the current query reference first and translate your criteria into that syntax. Supply clear criteria and a result limit.
Manage which optional storage OOMOL can use. You can change these choices from the footer at any time.