Provide known identifiers to retrieve available profile data and distinguish missing information from a match.
Copy a prompt into your agent with the oo Skill installed. Add your page links and source notes before running it.
Look up a domain and organize the available profile fields.
/oo FullContact: Enrich company domain [domain] with FullContact. Summarize available name, website, location, description, and employee information. If queued, report that status without assuming the profile is complete.
Read field-level match flags for identifiers you supply.
/oo FullContact: Use FullContact to verify the match between email [email] and phone [phone]. Explain the field-level match flags and distinguish missing signals from negative matches.
Set up oo CLI and the oo Skill in your agent.
Install OOMOL →Connect a FullContact API key.
Connect FullContact →Use /oo with the pages to read, the changes to make, and where to save the result.
Connection Guide →Choose Your Agent
The connection enriches company and person profiles and reads identity match, signal, and activity information. Some enrichment requests may be queued rather than return a completed profile.
Retrieve available company data by domain or person data by known identifiers.
Compare identifiers and inspect identity signals or activity scores.
Enrich a person profile with FullContact by sending one or more known identifiers.
Leina 
Wanta 
full_contact.enrich_person Enrich a company profile with FullContact by domain.
full_contact.enrich_company Compare person identifiers with FullContact and return field-level match flags.
full_contact.verify_match Resolve person identifiers with FullContact and return identity signal details.
full_contact.verify_signals Return FullContact activity scores for matched person identifiers.
full_contact.verify_activity No matching tools.
No. Fields depend on available matches and data coverage. Keep missing values distinct from known facts.
It means the request was accepted for processing, not that a completed profile is available. This connection does not expose a separate queue-result polling action.
An email, phone, known profile, or supported identity ID can be used. Name-based lookup also needs location information.
Manage which optional storage OOMOL can use. You can change these choices from the footer at any time.