Wiza
Wiza helps you find and export accurate contact data for prospects from LinkedIn, providing verified emails, phone numbers, and enriched professional information.
Verdict
Common use cases
- Build targeted outreach lists by job title and location
- Verify contact emails before cold email campaigns
- Enrich inbound leads with phone numbers and firmographics
- Research competitor hiring patterns by company and role
- Check API credit balance before bulk enrichment runs
Integration
- Vendor
- Wiza
- Category
- crm
- Auth
- API_KEY
- Tools
- 5
- Composio slug
wiza
Tools
- Get API Credits
Tool to get the number of remaining API credits in your account. Returns available credits for emails, phone numbers, and company enrichment. Use when you need to check remaining API credit balance.
- Get Individual Reveal
Tool to get the status and results of an individual reveal by ID. Returns enriched contact data including email, phone, job title, and company information when the reveal is completed. Use when you need to check the status or retrieve resul
- Get List Details
Tool to get the status and details of a list by its ID. Returns list metadata, status (queued, processing, completed), and statistics including enrichment level and email preferences. Use when you need to check the processing status or retr
- Search Prospects
Tool to search for prospects matching specific filters. Returns count and sample profiles based on job title, location, company, industry, and other criteria. Use when you need to find prospects that match specific professional criteria.
- Start Individual Reveal
Tool to start an individual reveal for real-time single contact enrichment. Provide name/company, email, or LinkedIn profile URL to get contact details including emails, phone numbers, and firmographic data. Use when you need to enrich a si
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Click 'Add Integration', search for Wiza, and select it from the catalog. 3. You'll be prompted to enter your Wiza API key — find this in your Wiza account dashboard under API Settings or Developer Tools. 4. Paste the key into Switchy and click 'Connect'. 5. Switchy will verify the key by checking your credit balance; if successful, you'll see a confirmation message. 6. Open any Space and type '@Wiza get my API credits' to test the connection — the assistant should return your remaining email, phone, and company enrichment credits. 7. To enrich a contact, use '@Wiza start an individual reveal for [LinkedIn URL or name/company]' and the assistant will queue the request and return results when processing completes. 8. For bulk workflows, start a list search with '@Wiza search for prospects matching [job title, location, industry]' to preview counts before committing credits.
What teammates see: by default, memories from Wiza are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Search Sales Prospects
@Wiza search for prospects with the job title 'VP of Sales' located in the San Francisco Bay Area working at companies in the SaaS industry with 50-200 employees.Open in a Space →
Enrich LinkedIn Profile
@Wiza start an individual reveal for the LinkedIn profile at https://www.linkedin.com/in/example-profile and return the contact's email, phone number, and current company information.Open in a Space →
Check Credit Balance
@Wiza get my current API credits and tell me how many email enrichments, phone enrichments, and company enrichments I have left.Open in a Space →
Review List Status
@Wiza get the details for list ID 12345 and show me the current status, total contacts, enrichment level, and how many have valid emails.Open in a Space →
Find Recruiting Targets
@Wiza search for prospects with the job title 'Senior Software Engineer' in New York City working at companies with 200-1000 employees and show me the total count.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@wiza search for prospects who are VP of Sales at Series B SaaS companies in the Bay Area with 50-200 employees
Found 847 prospects matching your criteria. Here's a sample of 5 profiles: Sarah Chen (VP Sales, CloudMetrics), Michael Torres (VP of Sales, DataFlow Systems), Jennifer Park (Sales VP, AuthStack)... Each profile includes current company, title, location, and LinkedIn URL. To enrich these contacts with verified emails and phone numbers, you can start a list reveal or individual reveals for specific prospects.
This example shows Wiza's prospect search filtering across job title, company stage, industry, location, and size. The search returns counts and sample profiles but doesn't include contact details until you run a reveal operation, which consumes API credits. Useful for qualifying your target audience before spending credits on enrichment.
@wiza start an individual reveal for Jennifer Park at AuthStack to get her verified email and direct phone number
Individual reveal started (ID: rev_8x4k2m). Status: processing. This typically completes in 30-90 seconds. I'll retrieve the results once ready... Reveal completed. Jennifer Park: verified email jennifer.park@authstack.io (deliverable), direct line +1-415-555-0847, mobile +1-650-555-2193. Job title: VP of Sales. Company: AuthStack (Series B, 120 employees, San Francisco). This reveal consumed 1 email credit and 1 phone credit from your account.
Individual reveals provide real-time contact enrichment and are ideal for high-priority prospects. Each reveal consumes credits (1 per email, 1 per phone number found). The operation has two steps: starting the reveal and retrieving results after processing. Check your credit balance first with the Get API Credits tool to avoid mid-campaign depletion.
@wiza check my remaining API credits and tell me if I have enough to enrich a list of 200 prospects with emails and phone numbers
Your Wiza account has 1,450 email credits, 890 phone credits, and 200 company enrichment credits remaining. For 200 prospects requesting both emails and phone numbers: you'd need 200 email credits (available) and 200 phone credits (available). You have sufficient credits for this enrichment. Note that actual consumption depends on data availability—if Wiza can't find a phone number for a contact, that credit isn't charged. Your current balance would support this list with a buffer of 1,250 email credits and 690 phone credits remaining.
Credit monitoring is essential before bulk operations. Wiza charges per data point found (email, phone, company data), not per attempt, so failed lookups don't consume credits. This example demonstrates planning for list enrichment costs. For ongoing campaigns, monitor credits regularly—running out mid-list leaves your enrichment incomplete and requires manual tracking of which contacts were processed.
Use-case deep-dives
When Wiza beats manual LinkedIn scraping for cold outreach
A 2-person sales team at a B2B SaaS startup needs 200 qualified leads per week for cold email campaigns. They filter by job title, company size, and industry in Wiza's search, then run bulk reveals to get verified emails and phone numbers. The MCP handles credit checks before each batch so they don't blow through their monthly allowance mid-week. This works when your ICP is narrow enough that Wiza's filters match your targeting criteria—if you need custom signals like "recently changed jobs" or "posted about X topic," you'll still need to enrich from LinkedIn Sales Navigator exports. The buying call: if your outbound motion is volume-based and your targeting fits standard firmographic filters, Wiza's API keeps your CRM fed without manual copy-paste.
Real-time contact enrichment for inbound demo requests
A 6-person revenue ops team at a mid-market company gets 40-60 demo requests daily through their website form. They capture name and company domain, then fire Wiza's individual reveal tool to backfill job title, direct phone, and LinkedIn URL before the lead hits Salesforce. The MCP polls reveal status and writes enriched data into the CRM record within 10 seconds of form submission. This setup breaks down if your inbound volume spikes above 200/day—Wiza's per-contact pricing gets expensive fast, and you'll want a cheaper append service for high-volume enrichment. The threshold: if your demo requests are under 1,500/month and sales needs full contact data before first touch, Wiza's real-time reveal justifies the cost per lead.
When Wiza's company enrichment supports multi-threading
A 4-person enterprise AE team works 20 named accounts at a time, each requiring outreach to 5-8 stakeholders across procurement, IT, and business units. They use Wiza's search to find contacts by job function within target accounts, then run reveals to get verified emails and mobile numbers for multi-threaded outreach. The MCP checks list status to confirm enrichment is complete before the AE starts sequencing. This approach works when your deal cycle is long enough to justify manual account planning—if you're running high-velocity SMB sales, the per-contact cost and setup time don't pencil. The call: if your sales motion is account-based and you need 5+ contacts per account with direct dials, Wiza's enrichment depth beats generic data providers.
Frequently asked
What does the Wiza MCP let me do in Switchy?
It lets your AI agents search for B2B prospects, enrich contact records with emails and phone numbers, and check your Wiza credit balance — all without leaving the chat. You can filter by job title, location, company, or industry, then pull enriched data (email, phone, LinkedIn, firmographics) for individual contacts or entire lists. Think of it as turning Wiza's lead-gen database into a conversational tool your team can query in plain English.
Do I need a paid Wiza account to use this MCP?
Yes. The MCP authenticates with a Wiza API key, which requires an active Wiza subscription. Free trials or demo accounts won't work if Wiza doesn't issue API keys on those plans. You'll also burn Wiza credits every time an agent enriches a contact or runs a reveal — the MCP doesn't change Wiza's pricing model, it just exposes the API through Switchy's chat interface.
Can the Wiza MCP export enriched contacts to my CRM?
No. The MCP retrieves contact data (emails, phone numbers, job titles) and surfaces it in the chat, but it doesn't write to Salesforce, HubSpot, or other CRMs. If you want enriched leads in your CRM, you'll need to copy-paste from the chat or use Wiza's native integrations outside Switchy. The MCP is read-only for prospecting and enrichment, not a sync tool.
How is this different from using Wiza's web app or Chrome extension?
The MCP brings Wiza's search and enrichment into a shared AI workspace where your whole team can run queries conversationally. Instead of logging into Wiza's dashboard or scraping LinkedIn one profile at a time, you ask an agent to find "CMOs at Series B SaaS companies in Austin" and get structured results instantly. It's faster for ad-hoc research, but you lose Wiza's UI features like saved lists and bulk export workflows.
Who on my team should connect the Wiza MCP?
Whoever owns your Wiza account and has the API key. Since every enrichment request burns credits from that account, you probably want one person (usually a sales ops lead or growth manager) to connect it, then share the Switchy workspace with reps who need prospect data. That way you control spend and avoid duplicate credit charges if multiple people connect separate Wiza accounts.