DataMerge AI
Sales IntelligenceEnrich companies and contacts through the DataMerge Company and Contact API, pulling firmographics from a domain and walking corporate hierarchies. Agents qualify an account against structure, not just a logo.
What This Integration Enables
DataMerge AI is the connector for teams whose accounts are companies rather than websites. Get Company Hierarchy walks a corporate family tree upward to the global ultimate parent and downward through subsidiaries, optionally including branch entities, capped by depth and filtered by country. That is a fundamentally different qualification signal from a job title. A job title tells you what someone does. A hierarchy tells you whether the account you are about to work is an independent buyer, a division that cannot sign, or a subsidiary of a group you already sell to. Sales teams that skip this question find out the expensive way, usually in a forecast review.
The rest of the surface is built to make that structural view cheap to maintain. Company and contact enrichment are asynchronous, so an agent starts a job, polls the status action, then reads each record with Get Company or Get Contact. DataMerge documents that reading a record by its ID consumes no credits, so an agent can re-read enriched data as often as a flow needs without paying twice. Contact search comes in two forms, and the difference matters: the standard search returns enriched people, while Start Unenriched Contact Search returns matching people without spending credits on their contact details, so a shortlist can be reviewed before anyone pays to reach it. Both unenriched actions sit behind the contact_search_unenriched beta flag, which Get Account Features will confirm, so a flow can fail early with a clear message instead of at the first call. Lists give the whole thing a working surface: create a list, pass its slug straight into an enrichment or search action so results file themselves, then move, prune or export items as accounts progress. These connectors let an agent maintain an account map rather than assemble one from scratch on every campaign.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Account creation from a bare domain
A domain arrives from a form fill or a list import. The agent calls Start Company Enrichment, polls Get Company Enrichment Status, and reads the matched company with Get Company. The record it writes into Salesforce carries the legal name rather than the marketing name, the registered address, the industry codes and the hierarchy identifiers. It then calls Get Company Hierarchy to establish whether the entity stands alone. If the parent already exists as an account, the agent links the two and flags the overlap instead of creating a duplicate. The duplicate account problem is not solved by better deduplication rules. It is solved by knowing which entities are the same company.
A shortlist reviewed before it is bought
An outbound team wants decision makers across 40 target domains. The agent calls Start Unenriched Contact Search with prioritised job titles and location filters, polls it, and reads back the matching people with no contact details attached and no credits spent. The shortlist goes to Google Sheets for the team to review, and the roles that are wrong get struck out. Only then does the agent run Start Contact Enrichment over the survivors, requesting work emails or phone numbers as required. Credits follow a decision that a person made rather than a filter that nobody checked.
Segments that keep themselves current
A campaign segment lives as a DataMerge list. The agent creates it with Create List, passes the returned slug directly into subsequent search and enrichment actions so results file themselves automatically, then uses Add Items To List and Move List Item to promote companies between stages as they qualify. Disqualified accounts are pruned with Delete List Item, which removes the company from the segment without touching the underlying enriched record, so the data survives and only the grouping changes. The segment is a live object the flow maintains, not a spreadsheet somebody exports on a Friday.
Human-in-Loop Highlight
Rolling a subsidiary up to its global ultimate parent is the single most consequential thing this connector does, and it is not a data write. It is a claim about who the customer is. Get it right and a team stops working an account that is already covered by a group agreement. Get it wrong and the agent reassigns ownership to a different region, addresses a decision maker who has no authority over the entity in question, or sends cold outreach into a company that is currently a paying customer through a parent nobody had mapped. Corporate structures also change through acquisition and restructuring, so a hierarchy that was accurate is not automatically still accurate. The agent therefore assembles the evidence and stops: "Get Company Hierarchy resolves [Subsidiary] to global ultimate parent [Parent]. [Parent] already exists in the CRM, owned by [Rep], with [N] open opportunities. Confirm the rollup and I will link the accounts and route ownership, or keep [Subsidiary] standalone?" Both the current owner and the parent's owner see it. This is human-in-the-loop applied where it earns its keep, because the agent can prove the structural link and only a person can decide what the company should do about it.
Agent Capabilities
20 actionsCompany Enrichment
4- Start Company Enrichment Queues an asynchronous company enrichment from a domain or company name and returns a job ID to poll. Optionally restricts matching to specific countries, or resolves the global ultimate parent instead of the queried entity. Country Codes and Global Ultimate are mutually exclusive.
- Get Company Enrichment Status Retrieves the status and results of a company enrichment job. Poll until success is true, at which point the result array holds the matched company records with legal name, address, industry codes, hierarchy identifiers and group financials.
- Get Company Fetches a single company record by DataMerge ID or by your own record UUID, supplying exactly one of the two. Fetching by record ID costs no credits and is the normal way to read back an enrichment result. Fetching by DataMerge ID may consume credits.
- Get Company Hierarchy Returns the corporate family tree for a company, walking up to the global ultimate parent and down through subsidiaries. Optionally includes branch entities, restricts to particular countries, caps the depth, or returns only subsidiaries. Used to establish whether an account is an independent buyer or part of a group.
Contact Enrichment and Search
7- Start Contact Enrichment Queues asynchronous enrichment for a batch of contacts and returns a job ID. Each contact is identified by name plus domain or company, or by LinkedIn URL, and can request work emails, personal emails or phone numbers.
- Get Contact Enrichment Status Retrieves the progress and record IDs of a contact enrichment job. Status moves through pending and processing to completed or failed, with counts of processed, successful and failed contacts. Pass each returned record ID to Get Contact.
- Get Contact Fetches a single enriched contact record by its record UUID. Reading a record consumes no credits, so it is safe to call repeatedly across a flow.
- Start Contact Search Queues an asynchronous search for contacts at a set of companies, identified either by a domain list or by a saved company list slug, and returns a job ID. Narrowed with location include and exclude filters and with prioritised job titles.
- Get Contact Search Status Retrieves the progress of a contact search job, including how many companies have been processed, how many contacts were found against the target, and how many were skipped.
- Start Unenriched Contact Search Queues a contact search that returns matching people without spending credits on their contact details, so a shortlist can be reviewed before enrichment. Gated behind the contact_search_unenriched beta flag.
- Search Unenriched Contacts Runs an unenriched contact search synchronously and returns matching contacts in the response with no job to poll. The only synchronous search endpoint, limited to 10 domains with at most 10 results per company, and gated behind the same beta flag.
Lists
7- List Lists Lists the saved company or contact lists on the account with their names, slugs, item counts and whether they are system lists. The slug returned here is what every other list action expects.
- Create List Creates a new company or contact list and returns it with a generated slug. Pass the slug into an enrichment or search action so results file themselves automatically. Defaults to a company list.
- Get List Items Returns the items in a list by slug, paginated with a default page size of 50 and a maximum of 100, sortable by any supported field. Used to export a saved segment.
- Add Items To List Adds companies or contacts to an existing list, supplying domains for a company list or contact record IDs for a contact list. Used to build a target segment incrementally from search and enrichment output.
- Move List Item Moves a single item between lists by source slug, item ID and target slug. Used to promote a company or contact between pipeline stages without re-adding and deleting it.
- Delete List Item Removes a single company or contact from a list without deleting the underlying record. Used to prune a segment as prospects are disqualified, with the option to re-add later.
- Delete List Permanently deletes a company or contact list. System lists cannot be deleted. The records themselves survive, so enriched data remains retrievable by record ID.
Account
2- Get Credit Balance Returns the credit balance broken down into one-off, recurring and rollover credits plus the combined total. Used to gate a large enrichment run or to alert when credits drop below a threshold.
- Get Account Features Lists the beta feature flags enabled on the account. Check this before relying on a gated action, such as unenriched contact search, so a flow fails early with a clear message.
Frequently Asked Questions
What can FlowRunner do with DataMerge AI?
FlowRunner agents can run Get Credit Balance, Get Account Features, and Start Company Enrichment in DataMerge AI, plus 17 more actions.
Does connecting DataMerge AI to FlowRunner require OAuth?
No. DataMerge AI connects to FlowRunner with an API key, no OAuth flow required.
Can DataMerge AI trigger a FlowRunner workflow automatically?
DataMerge AI doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with DataMerge AI
$100 in credits. No card required. Connect in minutes.