LeadOcean + Microsoft Dynamics 365: enrich contacts on a schedule

You get a Power Automate flow that finds Dynamics 365 contacts with a LinkedIn URL and no email, asks LeadOcean for each one, and writes the result back to Dataverse. The link is one HTTP action calling POST /v1/people/enrich. It runs on a schedule, skips contacts that already have an email, and never overwrites a value you typed.

This recipe uses Power Automate and the Dataverse connector, which offers List rows and Update a row (Microsoft Learn, September 2026). LeadOcean needs a free key.

How it works

1. Create a LeadOcean key. Sign up at app.leadocean.io/register. The free plan has 1,000 records, one-off, no card.
2. Add a LinkedIn column to Contact. Dynamics holds no standard LinkedIn field, so add a text column such as new_linkedinurl and fill it from your list.
3. Create a scheduled cloud flow. Add a Recurrence trigger. Daily at night suits a backlog.
4. Add List rows on Contacts. Filter to contacts that need data, and set Top Count to 100 so each run stays small.
5. Add an Apply to each loop with an HTTP action. POST the LinkedIn URL to LeadOcean with the x-api-key header.
6. Gate on email status. Continue only when the first email is verified or catch_all_valid. A 404 means LeadOcean holds nothing and costs nothing.
7. Add Update a row. Write email, phone and job title to the contact.
8. Test on five contacts. Set Top Count to 5, run the flow once, and open each record.

Licensing: a Power Automate Premium licence covers standard, premium and custom connectors. Dynamics 365 licences include only a limited set of Power Automate capabilities, listed in Microsoft's Power Platform Licensing Guide (Microsoft Learn, October 2026). Check yours before you build.

Configuration

Set the List rows filter in OData so only blank, enrichable contacts come back. emailaddress1 is the standard email column on Contact.

Table name:    Contacts
Filter rows:   emailaddress1 eq null and new_linkedinurl ne null
Top Count:     100

The HTTP action sends one identifier per call. The expression in the body is Power Automate's dynamic content for the new_linkedinurl column.

Method:   POST
URI:      https://api.leadocean.io/v1/people/enrich
Headers:  x-api-key: <your LeadOcean key>
          content-type: application/json
Body:     {
            "linkedin_url": "@{items('Apply_to_each')?['new_linkedinurl']}",
            "reveal_email": true
          }

Store the key in an environment variable or Azure Key Vault, not in the flow text. Test the same request from a terminal first.

curl -X POST "https://api.leadocean.io/v1/people/enrich" \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "content-type: application/json" \
  -d '{"linkedin_url":"https://www.linkedin.com/in/jane-doe","reveal_email":true}'

Send exactly one identifier. Two is a 400. reveal_email costs no extra record (LeadOcean docs, September 2026). Addresses come back best first, so the first entry is the one to write:

first(body('HTTP')?['data']?['contact_data']?['contact_emails'])?['email']

Field mapping

The response nests data under data.contact_data. Map these into Contact columns.

Dedupe: Dynamics 365 ships default duplicate detection rules for accounts and contacts, and you can add rules for other tables (Microsoft Learn, September 2026). This flow only updates existing rows, so it creates no new duplicates. Two habits keep it clean.

• Filter on emailaddress1 eq null. A contact with an email is never touched.
• Match by new_linkedinurl, one URL per contact. Two contacts sharing a URL will both be enriched, so clean the column first.

Cost at 10,000 rows

At 10,000 contacts, LeadOcean costs $0 for the first 1,000 records and $97 on Solo for the rest. Power Automate adds its own licence cost.

LeadOcean. A hit counts as one record. A miss is a 404 and costs nothing. The Free plan covers 1,000 records, once. Solo is $97 a month with no per-record price and a pace of 10k enrichments every 5 hours, so 10,000 rows fit in one run (LeadOcean pricing). The Free rate limit is 5 requests a second, so keep the loop's concurrency low.

Dynamics 365 and Power Automate. Power Automate Premium is $15 per user a month, paid yearly; the page shows no monthly-billed rate (Microsoft, October 2026). Dataverse reads and updates count toward Power Platform request limits. A licensed Dynamics 365 Sales Enterprise user gets 40,000 requests per 24 hours (Microsoft Learn, September 2026). A run that lists, updates and calls out for 10,000 rows is roughly 20,000 or more requests, so batch over two nights on a small tenant.

The request count is arithmetic from the limits above, not a measured run.

Troubleshooting

FAQ