> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to Wiza

The Wiza connector lets your AI agent act in each user's Wiza account. Each user connects their own Wiza access token once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 5 tools.

**Authentication:** Bearer Token
**Categories:** CRM & Sales
**Tools:** 5: 4 read, 1 write, 0 destructive
**Users sign in with:** Access token
**Built by:** Scalekit connector
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=WIZA)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the Wiza connection

   In **AgentKit > Connections**, create a Wiza connection. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

4. ### Authorize a user and make your first call

   **Node.js** (`quickstart.mts`)

   ```typescript
   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   import { createInterface } from 'node:readline/promises'

   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENVIRONMENT_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions

   const connector = 'wiza'
   const identifier = 'user_123'

   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize Wiza:', link)
   const rl = createInterface({ input: process.stdin, output: process.stdout })
   await rl.question('Press Enter after authorizing...')
   rl.close()

   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'wiza_company_enrichment',
     toolInput: {},
   })
   console.log(result)
   ```

   ```bash
   npx tsx quickstart.mts
   ```

   **Python** (`quickstart.py`)

   ```python
   import os
   from scalekit import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()

   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions

   connection_name = "wiza"
   identifier = "user_123"

   # Generate an authorization link for the user
   link_response = actions.get_authorization_link(
       connection_name=connection_name,
       identifier=identifier,
   )
   print("Authorize Wiza:", link_response.link)
   input("Press Enter after authorizing...")

   # Make your first call
   result = actions.execute_tool(
       tool_input={},
       tool_name="wiza_company_enrichment",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)
   ```

   ```bash
   python quickstart.py
   ```

   Each user opens the link once and enters their Wiza credentials there. See [Authorize a user](/agentkit/tools/authorize/) for the full flow and statuses.

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'wiza_company_enrichment',
  toolInput: {},
  connector: 'wiza',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="wiza_company_enrichment",
    tool_input={},
    connection_name="wiza",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `wiza_company_enrichment`

Enrich Company · Read-only

Look up firmographic data for one company.
Returns industry, size and size range, founding year, revenue range, funding, type, description, location, social links and domain.
Use to enrich a known company; use wiza_prospect_search to find people at companies. Costs 2 API credits only when company data is found.
Provide at least one of company_name, company_domain, company_linkedin_id or company_linkedin_slug.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `company_domain` (`string`, optional): Domain of the company to enrich. At least one identifier field is required.
- `company_linkedin_id` (`string`, optional): LinkedIn company ID of the company to enrich. At least one identifier field is required.
- `company_linkedin_slug` (`string`, optional): LinkedIn company slug taken from the company page URL. At least one identifier field is required.
- `company_name` (`string`, optional): Name of the company to enrich. At least one of company_name, company_domain, company_linkedin_id or company_linkedin_slug is required.

Example input: `{}`

### `wiza_get_credits`

Get Credits · Read-only

Get the remaining credit balances on the connected Wiza account.
Returns email credits, phone credits, export credits and API credits; email and phone credits may be the string 'unlimited'.
Use this to check the balance before starting reveals or searches, which consume credits.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `wiza_get_individual_reveal`

Get Individual Reveal · Read-only

Get the status and results of an individual reveal by its ID.
Returns status, is_complete, the person's name, title, location, emails with type and status, phone numbers, company details and remaining credits.
Use after wiza_start_individual_reveal; repeat until is_complete is true or status is failed.
Prerequisites: a reveal ID from wiza_start_individual_reveal.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `id` (`string`, required): ID of the individual reveal, as returned by wiza_start_individual_reveal in data.id.

Example input: `{"id":"<id>"}`

### `wiza_prospect_search`

Search Prospects · Read-only

Search Wiza's prospect database for people matching filters such as job title, seniority, location, company, industry, size, revenue and technologies.
Returns data.total (matching count) and, when size is greater than 0, profiles with full name, LinkedIn URL, job title, role, company name and website, location, plus api_credits used.
Use to find people before revealing contact details with wiza_start_individual_reveal. Use wiza_company_enrichment for a known company. At least one filter is required; size 0 returns only the count.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `additional_filters` (`object`, optional): Extra Wiza prospect filters merged into the filters object for options not listed above, such as years_of_experience_min, years_of_experience_max, school, major, linkedin_slug, company_annual_growth, department_size, funding_date, funding_stage, funding_type, last_funding_min, last_funding_max, funding_min, funding_max, company_summary, year_founded_start and year_founded_end. Use the same field names and value formats as the Wiza Prospect Search API. Example: {"years_of_experience_min": 5, "funding_stage": {"t": "last", "v": ["series_a"]}}.
- `company_industry` (`array`, optional): Company industries. Each item has v (a valid Wiza industry value such as 'financial services') and optional s ('i' default, or 'e').
- `company_location` (`array`, optional): Company locations. Each item has v, b (city, state, country, continent or group) and s ('i' or 'e').
- `company_size` (`array`, optional): Company headcount ranges. Allowed values: 1-10, 11-50, 51-200, 201-500, 501-1000, 1001-5000, 5001-10000, 10001+.
- `company_type` (`array`, optional): Company types. Allowed values: private, public, educational, government, nonprofit, public_subsidiary.
- `first_name` (`array`, optional): Exact first names to match.
- `job_company` (`array`, optional): Current company names to include or exclude. Each item has v (name) and s ('i' or 'e').
- `job_role` (`array`, optional): Job roles. Allowed values: customer_service, design, education, engineering, finance, health, human_resources, legal, marketing, media, operations, public_relations, real_estate, sales, trades.
- `job_title` (`array`, optional): Job titles to include or exclude. Each item has v (the title; wrap in double quotes inside the string for an exact match) and s ('i' include or 'e' exclude).
- `job_title_level` (`array`, optional): Seniority levels. Allowed values: CXO, Director, Entry, Manager, Owner, Partner, Senior, Training, Unpaid, VP.
- `last_company_change` (`string`, optional): Only people who joined their current company within this period. One of: `30d`, `60d`, `90d`, `180d`, `1y`.
- `last_name` (`array`, optional): Exact last names to match.
- `last_role_change` (`string`, optional): Only people whose current role began within this period. One of: `30d`, `60d`, `90d`, `180d`, `1y`.
- `location` (`array`, optional): Person locations. Each item has v (name: 'city, state, country', 'state, country' or 'country' depending on b), b (city, state, country, continent or group) and s ('i' or 'e').
- `past_company` (`array`, optional): Past company names to include or exclude; people who currently work there also match. Each item has v and s ('i' or 'e').
- `revenue` (`array`, optional): Company revenue ranges. Allowed values: $0-$1M, $1M-$10M, $10M-$25M, $25M-$50M, $50M-$100M, $100M-$250M, $250M-$500M, $500M-$1B, $1B-$10B, $10B+.
- `size` (`integer`, optional): Number of profiles to return, 0 to 30. Wiza defaults to 0, which returns only the total count without profiles; set 1 to 30 to get profiles (billed in API credits).
- `skill` (`array`, optional): Skills the person must have.
- `technologies` (`array`, optional): Technologies used by the company, as technology slugs. Each item has v (slug such as 'amazon-web-services') and optional s ('i' default, or 'e').

Example input: `{}`

### `wiza_start_individual_reveal`

Start Individual Reveal · Write

Start an asynchronous reveal that finds the email and/or phone number of one person and returns the reveal ID.
Returns the reveal id, its status (queued, resolving, finished or failed) and an is_complete flag; contact data is not included yet.
Identify the person by LinkedIn profile_url, by full_name plus company or domain, or by email. Poll with wiza_get_individual_reveal until is_complete is true. Consumes credits according to enrichment_level.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `enrichment_level` (`string`, required): How much to look up. 'none' returns profile data for a LinkedIn URL or email without emails or phone numbers; 'partial' finds email; 'phone' finds phone numbers; 'full' finds email and phone numbers. One of: `none`, `partial`, `phone`, `full`.
- `accept_personal` (`boolean`, optional): Set true to accept personal email addresses such as tcooke1960@gmail.com. If neither accept_work nor accept_personal is set, all email types are returned.
- `accept_work` (`boolean`, optional): Set true to accept professional email addresses such as tim.cooke@apple.com. If neither accept_work nor accept_personal is set, all email types are returned.
- `callback_url` (`string`, optional): URL that receives the reveal result when it completes. If omitted, the webhook URL from the Wiza account settings is used.
- `company` (`string`, optional): Company name of the person. Provide company or domain when identifying the person by full_name.
- `domain` (`string`, optional): Company domain of the person. Provide company or domain when identifying the person by full_name.
- `email` (`string`, optional): Email address of the person. Can be used alone to identify the person.
- `fair_key` (`string`, optional): Key that spreads throughput fairly across sub-groups such as end users or lists. Reveals are dispatched round-robin across distinct values; if omitted, they run in submission order.
- `full_name` (`string`, optional): Full name of the person. Must be combined with either company or domain when no profile_url or email is given.
- `profile_url` (`string`, optional): LinkedIn profile URL of the person. Use alone, or together with full_name and company/domain.

Example input: `{"enrichment_level":"none"}`

## Related

Other CRM & Sales connectors ([all 174](/agentkit/connectors/?category=crm-sales)):

- [Salesforce](/agentkit/connectors/salesforce/): Scalekit connector, OAuth, 74 tools
- [HubSpot](/agentkit/connectors/hubspot/): Scalekit connector, OAuth, 457 tools
- [Close](/agentkit/connectors/close/): Scalekit connector, OAuth, 103 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
