Skip to main content
The Data Legion app on Make brings person and company enrichment, plus free data cleaning, email hashing, and validation, into any Make scenario. Add a Data Legion module, create a connection with your API key, and map the fields earlier modules give you.
The app is not live yet. It is in Make’s review, and this page describes it ahead of launch. To talk about access now, email support@datalegion.ai.

Prerequisites

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

Connect

Add a Data Legion module to a scenario, select Create a connection, and paste your API key. Make checks it against GET /credits, which is free, and labels the connection with your team’s name. To try a scenario without spending credits, turn on Sandbox mode in the connection. The enrich modules then return sample records (Jane Sandbox, Sandbox Corp) 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.

Modules

We add no fee for using the app. Make counts module runs against your Make plan, as it does for any app.

Enrich a Person and Enrich a Company

Fill in the identifiers you have, mapping them from earlier modules: 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 outputs one bundle: the 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 later modules by name. When nothing matches, the module stops with a “not found” error (404), and the lookup uses no credits. To carry on with the next record, right-click the module, choose Add error handler, and pick Ignore to skip the record or Resume to output values you set instead.

Clean, Hash, and Validate

  • Clean data normalizes emails, phone numbers, names, profile URLs, domains, and the other fields you fill in. Default phone region applies to numbers without a country code and is US when left empty.
  • Hash an email normalizes an address and returns its SHA-256, SHA-1, and MD5 hashes, the format ad platforms take for audience matching.
  • Validate data 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.

Make an API Call

Make an API call reaches any Data Legion endpoint the other modules don’t cover, such as Person Search, with the connection’s key already attached. Enter a path such as /person/search (the base URL is filled in), the method, and the JSON body from the endpoint’s API reference.

Example Scenario: Enrich a Google Sheets List

  1. Google Sheets > Watch Rows (or Search Rows) reads new or existing rows.
  2. Data Legion > Enrich a person looks each person up by the email in the row.
  3. Google Sheets > Update a Row writes the job title, company, and LinkedIn URL back to the same row.

Errors and Rate Limits

The app shows the API’s own error message, with the status code. 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 check the connection. Enrich and the utilities each allow 100 requests per minute. When a scenario reaches the limit, Make delays its next run instead of turning it off. See Rate Limiting for details.

The App or the Data Legion API

The app covers enrichment and the free utilities inside scenarios, one record per bundle. Natural-language discovery and bulk delivery are on the Data Legion API, and Make an API call reaches those endpoints from a scenario.