LeadOcean + HubSpot: enrich records automatically

You get a HubSpot workflow that fires on a new contact and sends the email to LeadOcean. It writes job title, company domain, phone and email status back. It uses one custom code action, not a marketplace app. LeadOcean has no HubSpot listing, so the call is a plain HTTP request to https://api.leadocean.io.

How it works

The workflow has four parts: an enrollment trigger, a custom code action, property updates and a guard so a record is never enriched twice. HubSpot says custom code actions need a Data Hub Professional or Enterprise account (HubSpot docs, October 2026). No Data Hub? Use the script route at the end of this section.

1. Create a LeadOcean key. Sign up at app.leadocean.io/register. The free plan needs no card and gives 1,000 records.
2. Store the key as a secret. In the custom code action, click Add secret and paste the value of $LEADOCEAN_API_KEY. HubSpot exposes it to the code as process.env.<secret name> (HubSpot docs, October 2026).
3. Create a contact-based workflow. Enroll contacts when Email is known and a custom property leadocean_enriched_at is unknown. This is the dedupe guard.
4. Add a Custom code action. Language Node.js. Add email as an input property. Paste the code from the next section.
5. Add Edit records actions. Map each code output to a contact property (see the table below). HubSpot documents code outputs as inputs to Edit records. Set leadocean_enriched_at last, to today's date.
6. Test on a dedicated record, then turn the workflow on. HubSpot applies a test to the selected record, so make a throwaway contact first (HubSpot docs, October 2026). The test spends one LeadOcean record.

The script route skips workflows. Search contacts with no job title, enrich each email, then call POST /crm/v3/objects/contacts/batch/update with up to 100 contacts per request (HubSpot docs, October 2026). It costs no Data Hub seat. You run it yourself from cron or a CI job.

For a one-off list, use the Exports page in the LeadOcean app. Build filters, pick columns, see the record price, download a CSV and import it into HubSpot.

Configuration

The code below runs inside the custom code action. HubSpot lists axios as a supported Node.js library (HubSpot docs, October 2026). Replace LEADOCEAN_API_KEY with your secret name.

const axios = require('axios');

exports.main = async (event, callback) => {
  const email = event.inputFields['email'];
  let out = { leadocean_status: 'not_found' };

  try {
    const res = await axios.post(
      'https://api.leadocean.io/v1/people/enrich',
      { email: email, reveal_email: true },
      { headers: { 'x-api-key': process.env.LEADOCEAN_API_KEY } }
    );
    const c = res.data.data.contact_data || {};
    const job = (c.contact_current_experiences || [])[0] || {};
    const phone = (c.contact_phones || [])[0] || {};
    const mail = (c.contact_emails || [])[0] || {};
    out = {
      leadocean_status: 'found',
      job_title: job.job_title || '',
      company_domain: job.company_domain || '',
      phone: phone.phone || '',
      email_status: mail.status || ''
    };
  } catch (e) {
    if (!e.response || e.response.status !== 404) throw e;
  }
  callback({ outputFields: out });
};

Test the same call outside HubSpot first:

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@example.com","reveal_email":true}'

Send exactly one identifier per call: email, linkedin_url, phone or person_id (LeadOcean docs, September 2026). A person LeadOcean holds nothing for is a 404 and costs nothing, which is why the code catches it and moves on. reveal_email costs no extra record.

Field mapping

The response is one leadocean.person.v1 object under a data key. The fields below sit under data.contact_data (LeadOcean docs, October 2026).

HubSpot treats email as the primary unique identifier for contacts, so match on email and never create contacts from this workflow (HubSpot docs, October 2026). Use Update, not create. Run the enrich step once per record and let the date property block repeats, so a re-saved contact never spends a second LeadOcean record. LeadOcean does not refund bounced emails, so filter on leadocean_email_status first.

Cost at 10,000 rows

10,000 rows cost $97 on LeadOcean Solo, plus HubSpot Data Hub Professional if you use the workflow route. Solo allows 10k enrichments every 5 hours and 50k a week, so 10,000 fits one window. The first 1,000 run free on the Free plan.

HubSpot's list price comes from its Data Hub page, which shows one "starts at" figure and no separate yearly rate (HubSpot, October 2026). The workflow route totals $897 a month. The script route drops the $800. HubSpot API limits are 100 requests per 10 seconds per app on Free and Starter, and 190 on Professional. A daily cap applies per account (HubSpot docs, October 2026). Batching 100 contacts per update keeps 10,000 rows near 100 write calls.

Teams enriching more than 50k rows a week, Solo's weekly pace, should look at Agency at $497 a month. See pricing.

Troubleshooting

FAQ