FullEnrich

Let AI agents enrich B2B contacts through FullEnrich's waterfall enrichment API. Agents start bulk enrichment jobs from a name plus company or LinkedIn URL, retrieve verified work emails and phone numbers, and check remaining credits before launching large batches.

3 actions API key available

FullEnrich website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

A list of new prospects lands from an event scan, a form capture, or a territory build

The agent validates each row has a first name, last name, and at least one identifier, ideally a LinkedIn URL

Get Credits confirms the remaining balance covers the batch at the requested fields

The RevOps owner reviews the batch size, the enrich fields, emails only or emails plus phones, and the projected credit spend, then approves the launch

Start Bulk Enrichment kicks off the waterfall job and returns the enrichment_id

Get Enrichment Results polls until the job reaches a terminal status

Verified emails and phones write to the CRM, and contacts with no result route to a manual research queue

What This Integration Enables

Contact data tools disagree with each other, which is the entire argument for waterfall enrichment: FullEnrich queries multiple providers in sequence until it finds a verified work email or phone, so one vendor's gap does not become your gap. This connector makes that waterfall a step inside a flow rather than a tool someone visits. FlowRunner agents assemble batches from any source, launch asynchronous enrichment jobs, poll for results or take a webhook callback, and route what comes back, verified contacts to the CRM and outreach, misses to a human queue. The opinion embedded here: enrichment should happen at the moment a lead enters your system, not as a quarterly cleanup project. Data decays; the flow keeps up. - Enrich batches identified by name plus company domain, company name, or LinkedIn URL, with LinkedIn as the most reliable identifier - Choose fields per batch: work emails, phone numbers, or both, since phone lookups can consume additional credits - Check the credit balance programmatically before any launch - Poll asynchronously or receive a webhook callback when jobs complete - Carry confidence and source details into your CRM with every result, so reps know how much to trust a number before they dial it

Without FlowRunner

Enrichment as tab-switching Someone looks up prospects one at a time across two or three data tools, pasting whatever they find

Credit burn nobody watches Batches launch without a balance check, and the tool goes dark mid-campaign when credits run out

Single-source misses One provider's blank means a dead lead, even when another provider had the number

With FlowRunner

Waterfall enrichment as a pipeline step Batches run through multiple providers in sequence, and results flow into the CRM with confidence and source attached

Spend reviewed before it happens Every batch launches with the balance checked and a person signed off on the projected consumption

Misses become a routed queue Contacts with no result land in a research queue instead of silently staying empty

Use Case Scenarios

Event badge scans to sequenced outreach in one flow

The morning after a conference, the scan export lands in [Google Sheets](/integrations/google-sheets). The agent normalizes names and companies, checks the balance with Get Credits, and presents the batch for approval. On sign-off, Start Bulk Enrichment runs the waterfall, Get Enrichment Results collects verified emails, and the enriched contacts flow into [Instantly](/integrations/instantly) for the follow-up sequence while the full results log back to the sheet. Leads get contacted while the conversation is still warm, not after a two-week manual research cycle.

The CRM that fills its own gaps

A weekly sweep queries [HubSpot](/integrations/hubspot) for contacts missing a work email or phone. The agent builds the batch, prioritizing records with LinkedIn URLs since those resolve most reliably, gets approval on the credit spend, and launches the job. Returned emails and phones write back to each contact with source and confidence noted, and the contacts that came back empty are tagged for the SDR team's manual pass. The database stops decaying because repair is a scheduled flow, not a someday project.

Inbound leads enriched before the first touch

A demo request arrives with a name and company but a personal Gmail address. The agent immediately starts a single-contact enrichment job, polls Get Enrichment Results, and attaches the verified work email and direct line to the lead record before it hits the sales queue. The rep opens a complete record and posts the routing note to [Slack](/integrations/slack). Speed-to-lead stays measured in minutes, and nobody researches a prospect the waterfall already found. The same pattern extends to any intake surface: a webinar registration, a pricing-page chat, a partner referral, each one arrives enriched or flagged, never blank.

Human-in-Loop Highlight

Start Bulk Enrichment spends credits with every successful lookup, and phone numbers can consume more than emails, so a thousand-contact batch with both fields enabled is a real invoice launched by a single API call against a balance that does not refill itself. Worse, a sloppy batch, duplicates, contacts already enriched, rows with weak identifiers, burns the same credits for data you did not need. That is why in FlowRunner flows the launch is a decision, not a side effect: the agent assembles and validates the batch, calls Get Credits, projects the consumption, and puts the batch size, field selection, and balance in front of the RevOps owner through a [human-in-the-loop](/concepts/human-in-the-loop) step. Approval fires the job; the polling, the CRM writes, and the routing of misses all run unattended afterward. Single-contact enrichment on a live inbound lead flows straight through by policy, because one credit for speed-to-lead is a trade already decided. Batches spend at scale, and spend at scale waits for a person.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via email

Human decides

Agent resumes with decision

Agent Capabilities

3 actions

Enrichment

Start Bulk Enrichment Starts an asynchronous waterfall enrichment job for a batch of B2B contacts, each identified by name plus a company domain, company name, or LinkedIn profile URL. FullEnrich queries multiple data providers in sequence for verified work emails and phone numbers. Returns an enrichment_id; supply a webhook URL to be notified on completion instead of polling.
Get Enrichment Results Retrieves the status and results of a job by enrichment_id. While processing, status reads pending or in-progress; once finished, each contact carries its discovered emails and phones with confidence and source details. Poll until the job reaches a terminal status.

Account

Get Credits Returns the enrichment credits remaining on your account. The pre-flight check before any batch, since lookups consume credits per successful result and phone lookups may consume more. Also useful as a standing monitor: a scheduled balance check that alerts the team before the pool runs dry mid-campaign.

Frequently Asked Questions

What can FlowRunner do with FullEnrich?

FlowRunner agents can run Start Bulk Enrichment, Get Enrichment Results, and Get Credits in FullEnrich.

Does connecting FullEnrich to FlowRunner require OAuth?

No. FullEnrich connects to FlowRunner with an API key, no OAuth flow required.

Can FullEnrich trigger a FlowRunner workflow automatically?

FullEnrich doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with FullEnrich

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us