Prospect list builder

You have the Trayo MCP server connected. Carry out this recipe against the real API.

# Find companies or people you do not have, and keep the good ones

When to use: You are starting from a description ("Series B fintechs in Europe", "heads of data at logistics companies") rather than from records you already hold.
Cost: One search against your quota per `POST /v1/find` that RUNS — a search that ran counts whether or not its results were useful, so read the response before sending a second one. Each account you then import draws on the same quota, as on `batchCreateAccounts`.

## Steps - find: `target` plus a natural-language `query`; add `filters` to make any criterion exact. One ranked page of at most 50. Read-only: nothing is written by finding. Before you re-run a disappointing search, read the three fields that say why it was thin. `interpreted` is what Trayo actually read out of your sentence — a criterion missing from `interpreted.filters` was NOT enforced, and resending `interpreted.filters` as `filters` makes the search exact and reproducible. `truncated: true` means more matched than this search can show, so narrow rather than page deeper. `degraded: true` means part of the search failed or timed out, so a thin page may be an outage rather than an absence of matches; `notes` then carries a `search_degraded` entry, which is the only account of what went wrong. Use what came back or refine what you send — do not just spend another search on the same words, because a repeat is billed as a new search and some causes persist for a workspace and degrade every repeat. An unqualified query is the usual cause of a thin page: "GPU cloud and AI compute providers" comes back dominated by companies over 27,000 people, because nothing in it says how big; say "startup", or send `filters.headcount`, and the same search returns the companies you meant. (`droppedUnaddressable` counts rows removed for having no website at all — a large one means the sentence swept up directories and institutions.) `notes` is the fourth, and the one to open whenever any of the other three says something went wrong: it names a filter whose values were not all scanned to the end, a bare city name that turned out to mean several places, or the degradation `degraded: true` reports. A bare city is `"dublin"`, Ireland and Ohio, or `"newark"`, New Jersey and California. Pin one as `"newark|california"` or `"dublin||IE"`. Several values of one filter are a union, so one call with twenty industries returns what twenty single-industry calls return; you do not need to split a search unless `notes` says a value ran out of budget.
- batchCreateAccounts: Bring the companies in. Deduplicated on hostname, then on `linkedinHandle`; a repeat is `alreadyAdded`, not an error. [optional]
- batchCreatePeople: Bring the people in. A person needs an account to belong to, so create accounts first. [optional]
- createList: A named working set that outlives this session and shows up in the Trayo app under the user your key acts as.
- addListMembers: By `personId` or `accountId`, with `via: "find"` recording how they got there. Re-adding a member is a skip, so the same batch is safe to send twice.

## Then Hand the LIST to whatever acts on it — a CRM push, a campaign, a person — rather than your session's memory of it.

Show full prompt Show less Copy prompt Copied