Connect Data Legion to Make using the built-in HTTP module. This lets you call person and company enrichment APIs from any Make scenario.
Prerequisites
- A Make account
- A Data Legion API key
Person Enrichment Setup
Add the HTTP Module
Open your scenario and add a new module. Search for HTTP and select Make a request.
Set the following fields:
| Field | Value |
|---|
| URL | https://api.datalegion.ai/person/enrich |
| Method | POST |
See the Person Enrichment API reference for the full list of available fields.
Add two headers:
| Item | Key | Value |
|---|
| 1 | Content-Type | application/json |
| 2 | API-Key | Your Data Legion API key |
Body
Set Body type to Raw and Content type to JSON (application/json).
In the Request content field, enter the JSON body. You can type static values or map fields from a previous module using Make’s mapping panel:
{
"email": "jane.doe@example.com"
}
To map a value from a previous module (for example, an email field from a Google Sheets row), click the field in the mapping panel and Make inserts the reference automatically.
You can add more input fields to improve match accuracy:
{
"email": "jane.doe@example.com",
"first_name": "Jane",
"last_name": "Doe",
"company": "Acme Corp",
"birth_date": "1985-03-15"
}
To limit the response to specific fields, add include_fields to the body:
{
"email": "jane.doe@example.com",
"include_fields": "full_name,job_title,seniority_level,company_name,company_size,company_industry,work_email,mobile_phone,linkedin_url,city,state"
}
See the Person Enrichment API reference for all supported input fields.
Parse the Response
Toggle Parse response to Yes. This tells Make to convert the JSON response into structured data that you can map in subsequent modules.
The API returns:
{
"matches": [
{
"person": {
"full_name": "jane doe",
"job_title": "senior product manager",
"seniority_level": "senior",
"company_name": "tech company",
"work_email": "jane.doe@techcompany.com",
"mobile_phone": "+15551234567",
"linkedin_url": "https://www.linkedin.com/in/janedoe"
},
"match_metadata": {
"matched_on": ["email"],
"match_type": "exact",
"match_confidence": "high"
}
}
],
"total": 1
}
In the next module, use Make’s mapping panel to reference response fields. The path follows the JSON structure:
| Make Field Path | Description |
|---|
Data > matches[] > person > full_name | Full Name |
Data > matches[] > person > job_title | Job Title |
Data > matches[] > person > seniority_level | Seniority |
Data > matches[] > person > company_name | Company |
Data > matches[] > person > company_size | Company Size |
Data > matches[] > person > company_industry | Industry |
Data > matches[] > person > work_email | Work Email |
Data > matches[] > person > mobile_phone | Phone |
Data > matches[] > person > linkedin_url | LinkedIn URL |
If the email doesn’t match any records, the API returns HTTP 404. Use Make’s error handling (the wrench icon on the module) to route no-match responses, for example by adding an Ignore error handler to skip to the next record.
Company Enrichment Setup
The same approach works for company enrichment. Use the Company Enrich endpoint:
https://api.datalegion.ai/company/enrich
The request body takes a domain, name, LinkedIn ID, or ticker symbol. Add include_fields to limit the response:
{
"domain": "example.com",
"include_fields": "name,domain,legion_employee_count,industry"
}
In subsequent modules, map fields from Data > matches[] > company (e.g., legion_employee_count, industry).
See the Company Enrichment API reference for all supported input and output fields.
Example Scenario: Enrich a Google Sheets List
A common pattern: read rows from a spreadsheet, enrich each row, and write the results back.
- Google Sheets > Watch Rows (or Search Rows) — triggers on new rows or reads existing ones
- HTTP > Make a request — calls
POST /person/enrich with the email from step 1
- Google Sheets > Update a Row — writes enriched fields (name, title, company, phone) back to the same row
Use Make’s Iterator module if the API returns multiple matches and you need to process each one.
Rate Limits
The Data Legion API returns rate limit headers on every response (RateLimit-Remaining, RateLimit-Reset). For large batch scenarios, add a Sleep module between iterations or reduce the scenario’s execution frequency to stay within your API plan limits.
See Rate Limiting for details.