Most enrichment requests start as an event. Someone books a demo, a lead lands in a form, a new contact appears in the CRM, and the useful question is who this person is and where they work, answered before the next step runs. On Zapier, answering it used to take Webhooks by Zapier: a custom request with headers, a JSON body, and a response you picked apart by hand.
Data Legion now has its own app on Zapier. Add a Data Legion step to a Zap, connect it once with your API key, and map in the fields the trigger gave you. The profile comes back as named fields (full name, job title, company, work email, and so on) ready to map into the step after it.
Connecting it
Create an API key on the API Keys page of your Data Legion dashboard, then add a Data Legion step and sign in with the key. Zapier checks it against your account and names the connection after your team, which helps when one Zapier account holds keys for more than one team.
What each lookup returns and costs comes from your Data Legion account, the same as through the API. A lookup with no match is free. We add no fee for using the app; Zapier counts the step against your Zapier plan as it does for any app.
The actions
Find Person finds a person by an email, a phone number, a social profile URL, or a name with one more detail such as a company, school, city, or job title. Find Company finds a company by domain, name, social profile URL, or ticker. Both are Zapier searches: a match returns the full record with its match metadata, and no match returns nothing, so you decide in the step's settings whether the Zap stops there or carries on without it. Each takes a minimum match confidence and a list of fields the match must have, so a Zap can pass over a person without the work email it needs.
Three actions use no credits. Clean Record normalizes emails, phone numbers, names, profile URLs, and domains. Hash Email returns the SHA-256, SHA-1, and MD5 of a normalized address, which is what ad platforms take for audience matching. Validate Record checks fields before you spend a lookup on them.
A Zap that fills in new leads
The pattern most teams set up first:
- Trigger: a new form submission, a new row in a sheet, or a new contact in the CRM.
- Data Legion: Find Person looks the person up by the email from the trigger.
- Update the record in the CRM or sheet with the job title, company, and LinkedIn URL that came back.
To route leads by what came back, add a filter or paths after the enrich step, for example sending people at your target accounts to one channel and everyone else to another.
When the API fits better
The app is for lookups inside Zaps. When records need enriching the moment they arrive in your own system, or you need search over the whole dataset rather than lookups from records you already have, the Data Legion API is the better fit; the real-time pipeline post covers that design. The Webhooks setup in the Zapier docs page still works for anything the app doesn't cover.
Like every Data Legion product, the app never returns people who have opted out, and contact data is for lawful use under our Acceptable Data Use policy. Try it on a few contacts you already know: run the Zap on them and compare what comes back.