Create
Find new people at a provider and add them to the CRM, attached to the right account.
Companies you do not have yet. Your CRM holds the market you have already met. The accounts you should be selling to, and the people at them who actually own the problem, are not in it at all, so no report will ever show you the gap.
Create is the only tool that adds records rather than correcting them, which makes it the only one with no record scope to choose. It has search criteria instead.
Criteria are the provider's own vocabulary. Job title, management level, department, industry, headcount, revenue, geography, and whether the provider actually holds an email for the person. Rows combine the way you would expect: separate criteria narrow, several values in one criterion widen.
Matching comes before creating. A person who is already in your CRM is not created again, and a new contact is attached to the account they work at, with that account created if you do not hold it yet.
How a pass runs
The detail
Restraint
So the preview is the default posture rather than an optional extra.
The provider will happily tell you that sixteen thousand people match your criteria. Creating sixteen thousand contacts is almost never what anybody wanted, and it is expensive in two currencies at once: provider credits, and the cleanliness of the CRM you just spent this whole product making correct.
So a run is capped, the preview reports the real number before anything is spent, and the run can be held for approval so that a person sees the count before a single record exists.
For agents
Reads are free and need no permission to write. Anything that changes a record is a separate grant.
list_search_criteria what the provider can be asked readpreview_records_run how many match, and how many you would create readcreate_records_run a run with criteria and a cap writedispatch_run start it writeWhere to start
The readiness scan runs detection against your own CRM and reports what it finds, before anything is merged.