LeadOcean + beehiiv: enrich newsletter subscribers with role and company

You get a beehiiv publication where each new subscriber is checked against LeadOcean, and the job title, company and company domain are written back to custom fields. You then segment your list by seniority and sell sponsorships against it. LeadOcean needs a free key. beehiiv webhooks need the Lite plan or above (beehiiv docs, September 2026).

How it works

1. Create the custom fields. In beehiiv, add job_title, company and company_domain. A field sent in an update that does not exist already is dropped, not created (beehiiv docs, September 2026).
2. Point a webhook at your automation. In Settings > Webhooks, add an endpoint for the subscription.created event. In Make, use a Custom Webhook module and paste its URL there (beehiiv docs, September 2026).
3. Call LeadOcean. Add an HTTP "Make a request" module (Make docs, September 2026). POST the subscriber's email to /v1/people/enrich.
4. Skip the misses. A person LeadOcean holds nothing for is a 404 and costs nothing. Stop the scenario on a 404 with a filter.
5. Write back to beehiiv. Send a PUT to the subscription with the three values as custom_fields.
6. Test on five subscribers, then switch the scenario on.

Configuration

Step 3, the LeadOcean call. {{1.email}} stands for the email from the webhook.

Method:   POST
URL:      https://api.leadocean.io/v1/people/enrich
Headers:  x-api-key: <your LeadOcean key>
          content-type: application/json
Body:     { "email": "{{1.email}}" }

Step 5, the write-back. Map the publication and subscription ids from the webhook payload in Make.

curl -X PUT "https://api.beehiiv.com/v2/publications/$PUBLICATION_ID/subscriptions/$SUBSCRIPTION_ID" \
  -H "Authorization: Bearer $BEEHIIV_API_KEY" \
  -H "content-type: application/json" \
  -d '{"custom_fields":[
        {"name":"job_title","value":"VP Marketing"},
        {"name":"company","value":"Acme"},
        {"name":"company_domain","value":"acme.com"}]}'

To test the LeadOcean half alone:

curl -X POST "https://api.leadocean.io/v1/people/enrich" \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "content-type: application/json" \
  -d '{"email":"jane.doe@acme.com"}'

Send one identifier per call. Two is a 400 (LeadOcean docs, September 2026). LeadOcean's docs list a work email as the email input. Many subscribers sign up with webmail, so expect misses on those.

Field mapping

See person enrichment for the full record.

Cost at 10,000 rows

10,000 subscribers cost LeadOcean at most 10,000 records. Misses are free, so the real number is lower. Free covers the first 1,000 records for life. Solo is $97 a month and Agency is $497 a month, both with a fair-use pace and no per-record price (LeadOcean pricing).

beehiiv. Webhooks need Lite, listed at $49 a month billed yearly (beehiiv pricing, October 2026). The API rate limit is 30 requests a minute on Free and 180 on Lite (beehiiv docs, September 2026). A backfill of 10,000 existing subscribers at 180 a minute takes about an hour per call type.

Make. This scenario runs three modules per subscriber, so 10,000 subscribers is about 30,000 module runs on your Make plan. Size the plan on Make's pricing page.

Troubleshooting

FAQ