LeadOcean + HubSpot: find company lookalikes

You get a HubSpot workflow that takes a company you already sell to and creates similar companies in HubSpot. LeadOcean does the matching: same industry, same headcount bracket, same headquarters country. There is no HubSpot listing for LeadOcean, so the call is a plain HTTP request to https://api.leadocean.io from one custom code action.

How it works

The trigger is a checkbox on the seed company. The action reads the seed from LeadOcean, searches for matches and writes them to HubSpot. HubSpot says custom code actions need a Data Hub Professional or Enterprise account (HubSpot docs, October 2026).

1. Create a LeadOcean key. Sign up at app.leadocean.io/register. No card, 1,000 records.
2. Add two secrets. In the custom code action, click Add secret. Add LEADOCEAN_API_KEY and a HubSpot private app token with company write scope. Secrets reach the code as process.env variables (HubSpot docs, October 2026).
3. Create a company-based workflow. Create a company property lookalike_seed (single checkbox). Enroll companies where it is true and Company domain name is known.
4. Add a Custom code action. Language Node.js. Add domain as an input property. Paste the code below.
5. Size the list first. Call GET /v1/companies/count with the same filters. It is free and returns an exact total, so you know how many records a run will spend.
6. Test on one seed, then turn it on. A test spends up to 26 LeadOcean records: 1 seed and 25 matches.

LeadOcean matches on firmographic filters. It is not a model score. Say that to whoever reads the list.

Configuration

HubSpot lists axios as a supported Node.js library (HubSpot docs, October 2026). Company creation is POST /crm/v3/objects/companies, and domain is the unique identifier HubSpot uses to avoid duplicates (HubSpot docs, October 2026).

const axios = require('axios');
const LO = { headers: { 'x-api-key': process.env.LEADOCEAN_API_KEY } };
const HS = { headers: { Authorization: 'Bearer ' + process.env.HUBSPOT_TOKEN } };

exports.main = async (event, callback) => {
  const domain = event.inputFields['domain'];

  // 1 record: the seed
  const seed = (await axios.post('https://api.leadocean.io/v1/companies/enrich',
    { domain }, LO)).data.data.company_data;

  // up to 25 records: the lookalikes
  const found = (await axios.post('https://api.leadocean.io/v1/companies/search', {
    industry: [seed.company_industries[0].name2],
    employeeRange: [seed.company_employees.number_of_employees_code],
    hqCountry: [seed.company_primary_address.country_code],
    hasMailableContacts: true,
    limit: 25,
    fields: ['company_data.company_name', 'company_data.company_domain']
  }, LO)).data.data;

  let created = 0;
  for (const c of found) {
    const d = c.company_data;
    if (!d.company_domain || d.company_domain === domain) continue;
    try {
      await axios.post('https://api.hubapi.com/crm/v3/objects/companies',
        { properties: { name: d.company_name, domain: d.company_domain } }, HS);
      created++;
    } catch (e) { /* duplicate or bad row: skip it */ }
  }
  callback({ outputFields: { created } });
};

The seed fields come from company_data: company_industries[0].name2, company_employees.number_of_employees_code and company_primary_address.country_code (LeadOcean docs). Any of them can be null, so guard them in production. Check the same search outside HubSpot first:

curl -X POST "https://api.leadocean.io/v1/companies/search" \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "content-type: application/json" \
  -d '{"industry":["Software Development"],"employeeRange":["51-200"],"hqCountry":["US"],"limit":25}'

Industry and headcount values are exact strings. Look them up free with list_enum_values or GET /v1/enums (LeadOcean docs, September 2026).

Field mapping

Cost at 10,000 rows

10,000 lookalikes cost $97 on LeadOcean Solo, plus HubSpot Data Hub Professional. Take 400 seeds at 25 rows each: 10,000 search records plus 400 seed lookups. Solo allows 100k search records every 5 hours (LeadOcean pricing). Free stops at 1,000 records, which covers about 38 seeds.

Teams running many seeds a day should read the Agency plan on the pricing page.

Troubleshooting

FAQ