> ## Documentation Index > Fetch the complete documentation index at: https://docs.revyops.com/llms.txt > Use this file to discover all available pages before exploring further. # Wiza > Connect a Wiza API key so Find data workflow steps can look up a person's email, mobile phone or LinkedIn URL. ## What This Integration Does Wiza is a data provider. Connecting it lets a workflow's [Find data step](https://docs.revyops.com/user-guide/workflows.md#find-data-step) look a person up with Wiza and add the email, mobile phone or LinkedIn URL it finds to that person in RevyOps. Add **Wiza** to the step's **Providers, in order**. Wiza is connected per workspace. Each workspace pastes its own Wiza API key, and Find data steps for that workspace that use Wiza spend API credits from that Wiza account. > [!NOTE] > > Wiza is in early access: it is off for every agency until a super admin switches it on. Until then its tile is locked with "Early access. Contact us to turn it on." and Find data steps pass Wiza over with "Wiza is not available on your plan. Ask your agency admin." > Wiza only appears on the Integrations page when Workflows access is switched on for your agency, because it is used by workflow steps only. ## Setup **1. Get an API key** Sign in at **wiza.co**, open **Settings**, then **API**, and click **New API Key**. Find data spends the account's **API credits**, which are separate from the email and phone credits used in Wiza's own app. An account with no API credits gets "Wiza has no credits left on this account, or a payment is due" on every lookup. **2. Open the integration** Go to **Settings → Integrations**, find the **Data Providers** section and open **Wiza**. **3. Save the key** Paste the key and click **Save key**. RevyOps saves it, then checks it against your Wiza credit balance, which costs nothing, and shows **Key saved and checked.** If Wiza refuses the key or can't be reached, the key is still saved and the panel says what went wrong. The panel shows **API key connected** once a key is saved. Click **Remove**, then **Remove key** to confirm, to delete the key; Find data steps then pass Wiza over with "No Wiza API key connected" until a key is saved again. ## How A Person Is Looked Up Each person is one Wiza lookup. RevyOps sends the best thing the person has: their LinkedIn URL, or else their full name and company domain (with their email, if they have one), or else their email alone. A person with none of these is skipped with the reason "Wiza needs a LinkedIn URL, an email, or a full name and company domain", and nothing is spent. The step asks Wiza only for what it wants: an email, a mobile phone, or both. Wiza says a work email takes about 25 seconds and can take up to 380, and a personal email about 4 seconds and up to 15. The step waits up to 110 seconds for each lookup. | What the step finds | Wiza API credits | | - | - | | **Email** | 2 when a valid email is found, nothing otherwise. A risky email comes back free | | **Mobile phone** | 5 when a number is found, nothing otherwise | | **LinkedIn URL** | 1 when only a LinkedIn URL is asked for and Wiza matches the profile, nothing otherwise | Every Wiza answer includes the person's LinkedIn URL. When the step wasn't asked for it but the person has none, it is added too, as found on the way. ## Email Status Wiza checks every email it returns. The result becomes the new email's status from Wiza: | Wiza result | Email status | | - | - | | valid | **Valid** | | risky | **Risky** | Nothing needs mapping: these are Wiza's only two results for a found email. When Wiza has both, the valid one is added. An email Wiza marks as personal, such as a Gmail address, is marked personal in the run log and the test results; a work email is marked business. ## When Wiza Says No | Wiza answer | What happens | | - | - | | The key is refused | The step fails with "Wiza refused the API key. Reconnect Wiza under Integrations." | | No credits left, or a payment is due | The step fails with "Wiza has no credits left on this account, or a payment is due. Top up Wiza, then rerun." | | The seat is paused, or there is no subscription or payment method | The step fails with Wiza's own reason | | Wiza has not finished after 110 seconds | The lookup is skipped with the reason "Wiza had not finished after 110 seconds, not added". It is not retried, because Wiza charges for the first lookup when it finishes and would charge again for a second | | Wiza did not confirm a lookup was started, because the request timed out or the reply could not be read | The step fails with "Wiza did not confirm the lookup in time; not retried so it is not paid twice." | | Wiza's queue is full, or Wiza is down | The step waits and tries again | Wiza's API runs 5 lookups at once on its starter plan and queues the rest. RevyOps starts one Wiza lookup every 6 seconds for each workspace, so 100 people take about 10 minutes. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.