LeadOcean + Facebook Lead Ads: reverse email lookup on every new lead

A Make scenario can send each Facebook Lead Ad email to LeadOcean and get back the person's name, LinkedIn URL, job title and employer. Lead forms mostly collect Gmail and Yahoo addresses, so the form alone tells a rep nothing. One HTTP call per lead fixes that. The free plan covers 1,000 leads, no card.

How it works

The scenario has three modules: Facebook Lead Ads "Watch Leads", HTTP "Make a request", and one module for your destination. A filter between the first two keeps work addresses out, so you spend records only on personal emails.

1. Get a key. Sign up at app.leadocean.io and create a key. Free keys get search and enrich scopes. The reverse lookup needs enrich.
2. Add the trigger. In Make, add Facebook Lead Ads "Watch Leads". Connect your Facebook account, then pick the Page and the lead form. Make documents the app as a way to monitor leads, and it needs a Business Manager account.
3. Filter personal domains. Put a filter after the trigger. Pass only emails ending in gmail.com, yahoo.com, hotmail.com, outlook.com or icloud.com. Edit the list for your market.
4. Add the HTTP module. Add HTTP "Make a request". Use the GET request below and map the lead's email into the email query parameter. Turn on "Parse response".
5. Handle a miss. If nobody holds the address, LeadOcean answers 404. Add an error handler on the HTTP module so one miss does not stop the scenario.
6. Send the result on. Append a row to Google Sheets, or create a contact in your CRM. Map the fields from the table below.
7. Test, then switch on. Click "Run once", submit a test lead on the form, and check the row. Then turn the scenario on.

Meta's own docs say leads can be read with webhooks or a bulk export. Make's module uses the webhook route, so a lead arrives when it is submitted.

Configuration

This is the HTTP module request. The curl command is the same call, so you can test your key before you build anything. The values are placeholders.

curl -s -G "https://api.leadocean.io/v2/people/reverse" \
  --data-urlencode "email=jane.doe@gmail.com" \
  -H "x-api-key: $LEADOCEAN_API_KEY"

A match returns the shape below, with placeholder values. Every identity field can be null. Each lookup costs one record, a miss included, the same as an enrichment (LeadOcean API reference, October 2026).

{
  "success": true,
  "data": {
    "person_id": "1234567",
    "linkedin_url": "https://www.linkedin.com/in/jane-doe",
    "full_name": "Jane Doe",
    "job_title": "Finance Manager",
    "company_name": "Acme",
    "company_domain": "acme.com",
    "matched": { "email": "jane.doe@gmail.com", "status": "verified", "type": "personal" },
    "matched_in_record": true
  }
}

The lookup returns identity, not a work email or a phone. For those, call POST /v1/people/enrich with the returned person_id, or use GET /v2/people/phone.

Field mapping

Cost at 10,000 rows

For 10,000 personal-email leads, LeadOcean covers the first 1,000 lookups on Free and the rest on Solo at $97 a month. FullEnrich's list price for the same job is $499 a month if every address matches.

Sources: LeadOcean pricing, FullEnrich pricing and FullEnrich credit costs, September 2026. The FullEnrich figure assumes all 10,000 match; it charges nothing when it finds nobody. Make bills its own credits for each module run on top of either, at the rates on Make's pricing page. The billed-yearly price is for 120,000 credits a year. LeadOcean publishes no match rate, so test a sample of your own leads first.

Troubleshooting

FAQ