LeadOcean + Retool: enrich records automatically

You get a Retool Workflow that runs on a schedule. It picks the database rows that are not enriched yet and calls LeadOcean for each one. It writes the current job title, company domain, phone and email status back to the row. Retool Workflows support schedule triggers, a Loop block and Resource query blocks, the Free plan included (Retool docs, September 2026). That is the whole integration. No extra tool sits between them.

How it works

The recipe has one query to read, one loop to enrich and one query to write. The loop calls POST /v1/people/enrich once per row. A 404 means LeadOcean holds nothing for that person and costs nothing.

1. Add the resource. Create a REST API resource with base URL https://api.leadocean.io, Authentication set to None, and a global header x-api-key holding your key. Global headers go on every request. Turn on Sanitize custom headers to keep the key out of logs (Retool docs, October 2026).
2. Create the workflow and a schedule trigger. Open the startTrigger block and add a Schedule trigger. Interval mode runs every n minutes, hours, days, weeks or months. Cron mode takes cron syntax and a timezone (Retool docs, September 2026).
3. Read unenriched rows. Add a Resource query block on your database resource. Select rows where leadocean_enriched_at is null and email is not null, with a LIMIT. This is the dedupe guard.
4. Add a Loop block over the rows. Reference the query result as the array. Inside, {{ value.email }} is the current row. Set Execution mode to Batch, with a batch size and a batch delay, so you stay under the rate limit (Retool docs, September 2026).
5. Call LeadOcean inside the loop. Add a Resource query on the REST API resource: POST /v1/people/enrich with the JSON body below.
6. Write back. Add a second Resource query that updates the row by primary key. Always set leadocean_enriched_at, even on a 404, so a miss is not retried every run.
7. Run it once by hand. Test with LIMIT 5, check the rows, then raise the limit and switch the schedule on.

Retool's Loop docs say parallel mode suits small data sets and can hit API limits on large ones. Sequential and Batch modes take an optional delay for that reason.

Configuration

The request body for step 5. Send exactly one identifier per call: email, linkedin_url, phone or person_id (LeadOcean docs, September 2026).

{
  "email": "{{ value.email }}",
  "reveal_email": true
}

Test the same call from a terminal before you build anything:

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","reveal_email":true}'

reveal_email costs no extra record. Add the two columns to your table first: leadocean_enriched_at (timestamp) and leadocean_email_status (text).

Field mapping

The response is one leadocean.person.v1 object under a data key (LeadOcean docs, September 2026).

Match on a stable primary key in your table, not on the email, so a changed address never creates a second row. LeadOcean does not refund bounced emails, so read the status before sending.

Cost at 10,000 rows

10,000 rows cost $97 on LeadOcean Solo, which allows 10k enrichments every 5 hours and 50k a week. The first 1,000 rows run free on the Free plan, which is one-off and needs no card. Solo is 50 requests a second and Free is 5, so set the batch delay to match.

Retool counts a workflow run each time a triggered workflow executes successfully, and steps are unlimited on the Free plan. So a daily run over 10,000 rows adds about 30 runs a month, well inside the Free allowance.

Above 50k enrichments a week, look at Agency at $497 a month. See pricing.

Troubleshooting

FAQ