Skip to main content
The Data Legion app on Zapier brings person and company enrichment, plus free data cleaning, email hashing, and validation, into any Zap. Add a Data Legion step, connect it once with your API key, and map the fields your trigger gives you.

​
Prerequisites

  • A Zapier account
  • A Data Legion API key, from API Keys in the dashboard

​
Connect

Add a Data Legion step to a Zap and choose Sign in. Paste your API key. Zapier checks it against GET /credits, which is free, and names the connection after your team, which helps when one Zapier account holds keys for more than one team. To try a Zap without spending credits, turn on Sandbox Mode in the connection. Find Person and Find Company then return sample records with every field a real record has, and use no credits. Turn it off for real lookups. If your API key is limited to certain endpoints, add /sandbox/person/enrich and /sandbox/company/enrich to it.

​
Actions

We add no fee for using the app. Zapier counts each step against your Zapier plan, as it does for any app.

​
Find Person and Find Company

Both are Zapier searches. Fill in the identifiers you have, mapping them from earlier steps: A domain matches a company more reliably than a name. A birth date can be a full date, a year and month, or a year (1985-03-15, 1985-03 or 1985). Options:
  • Minimum Match Confidence drops matches below High, Moderate, or Low confidence.
  • Required Fields takes comma-separated fields a match must have, such as work_email or phones.type:mobile for a person and domain,socials, type:public or socials.network:linkedin for a company. A match without them counts as a no-match.
  • Industry (company only) narrows a match on company name, for example software development. It isn’t a lookup on its own.

​
Output

A match returns the full person or company record as named fields (full_name, job_title, company_name, work_email, and so on, from the Person Schema or Company Schema), plus match_metadata. Map them into the next step by name. When nothing matches, the search returns no result. In the step’s settings, choose whether the Zap stops there or carries on without it. To route leads by what came back, add a Filter or Paths step after the search.

​
Clean, Hash, and Validate

  • Clean Record normalizes emails, phone numbers, names, profile URLs, domains, and the other fields you fill in. Default Phone Region (for example US) applies to numbers without a country code.
  • Hash Email normalizes an address and returns its SHA-256, SHA-1, and MD5 hashes, the format ad platforms take for audience matching.
  • Validate Record checks contact and company fields and returns errors, warnings, and suggested fixes before you spend credits on enrichment.
See Clean, Hash Email, and Validate for the response shapes.

​
Example Zap: Enrich New CRM Contacts

  1. Trigger: a new contact in HubSpot, Salesforce, or Pipedrive, a new form submission, or a new row in a sheet.
  2. Data Legion: Find Person looks the person up by the email from the trigger.
  3. Update the record with the job title, company, and LinkedIn URL that came back.

​
Errors and Rate Limits

The app shows the API’s own error message. Running out of credits (402) or calling an endpoint the key isn’t scoped to (403) says so, and an invalid key (401) asks you to reconnect. Enrich and the utilities each allow 100 requests per minute. Zapier retries a rate-limited step on its own, following the API’s Retry-After header. See Rate Limiting for details.

​
The App or the Data Legion API

The app covers enrichment and the free utilities inside Zaps, one record per step. Search, natural-language discovery, and bulk delivery are on the Data Legion API. To call an endpoint the app doesn’t cover, use Webhooks by Zapier with the Custom Request event: method POST, the endpoint’s URL (for example https://api.datalegion.ai/person/search), headers Content-Type: application/json and API-Key set to your key, and Payload Type Raw with the JSON body from the endpoint’s API reference. Zapier parses the response, and you map fields by their path, such as matches__0__person__full_name.