--- title: "uProc Integration" description: "Verify, validate, and enrich contact data through uProc's catalog of hundreds of processors across email, phone, company, IP, and geolocation. Agents verify deliverability, infer gender, search company data, and run any processor by name." url: https://flowrunner.ai/integrations/uproc date_modified: 2026-08-01T02:40:32-07:00 --- # uProc [Sales Intelligence](https://flowrunner.ai/integrations/category/crm-sales) Verify, validate, and enrich contact data through uProc's catalog of hundreds of processors across email, phone, company, IP, and geolocation. Agents verify deliverability, infer gender, search company data, and run any processor by name. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 8 actions · Basic auth · available [uProc website](https://uproc.io/) · [Platform Documentation](https://docs.uproc.io) · Capability data verified 2026-07-14 1. Batch of raw contacts pulled from a sheet or import 2. Agent calls Get Profile to confirm the API key is valid and credits remain 3. Agent calls Verify Email on each address for a deliverability verdict 4. Agent calls Verify Phone with the country code for line validity 5. Agent infers gender and appends company data where needed 6. Cleaned list summarized for the list owner 7. Owner approves before verification results purge contacts from the live list ## What This Integration Enables Agents use uProc to clean and enrich contact data across many data types without stitching together separate tools. Verify Email checks whether an address exists and can receive mail, and Verify Phone checks a number's validity when given its ISO country code. Get Gender by Name infers likely gender from a first name, and Company Search looks up company records by name within a country. When no dedicated wrapper fits, Run Tool reaches any processor in the catalog by its group-tool name with an arbitrary params object, which covers text transforms, IP and geolocation lookups, image tools, and more. List Groups and List Tools let an agent discover the available processors and their parameters, and Get Profile confirms the credentials and reports the remaining credit balance before a batch run. ### Without FlowRunner **Dirty contact lists**: Imports carry undeliverable emails and invalid phone numbers no one has checked **One tool per task**: Email, phone, and company checks each live in a separate service **Blind credit spend**: Batch verification runs without confirming the balance first ### With FlowRunner **Verified contacts**: Every email and phone is checked for validity before the record is used **One runner, many tools**: A single generic runner reaches the whole uProc catalog from one integration **Credit-aware batches**: The agent confirms the balance before committing a batch of checks ## Use Case Scenarios ### List Hygiene Before the CRM An agent pulls a list of leads from a sheet, confirms its credit balance with Get Profile, and runs Verify Email on each address. It keeps only the deliverable contacts and writes them to a clean list, leaving the undeliverable ones out of the CRM entirely. The controller of the pipeline gets contacts that will actually receive mail instead of a list that bounces on the first send. ### Validate and Enrich Before Contact Creation Before creating a CRM contact, an agent calls Verify Phone with the number and its country code to confirm the line is reachable, then Get Gender by Name to enrich the record. Only records that pass validation and enrichment become contacts. The team keeps low-quality records out of the CRM without manual review of each one. ### Any Processor Through One Runner An agent needs a data operation with no dedicated wrapper, such as a geolocation lookup or a text normalization. It calls List Tools to find the right processor and its parameters, then Run Tool with the group-tool name and a params object to execute it. The whole uProc catalog is reachable from the same workflow, so a new data need does not require a new integration. ## Human-in-Loop Highlight Verification tells an agent which contacts look invalid, but acting on that verdict by removing contacts from a live list is a consequential step, not a lookup. Before an agent lets a batch of verification results purge records from a working list, it pauses for a human. This is FlowRunner's human-in-the-loop as a scale lever: the agent runs the checks across the whole list, and a person confirms the one action that deletes data. The agent messages the list owner through Slack: "uProc flagged \[N\] contacts as undeliverable or invalid. Approve removing them from the \[List\], or keep any you want to hold for a second check." The owner reviews and approves, and the list loses only the records a human agreed to drop. The agent does the verification at scale; the human owns the decision to remove real contacts. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via Slack Human decides Agent resumes with decision ## Agent Capabilities 8 actions ### Tools 1 - **Run Tool** Run any uProc tool (processor) by name and return its processed result. The fully generic runner covers the entire catalog across email, phone, company, IP, geolocation, text, and image. Provide the processor name in group-tool form, such as "email-check-exists", and a params object with the inputs that tool expects. Each call consumes credits. Use it when no dedicated wrapper fits the task. ### Email 1 - **Verify Email** Check whether an email address exists and can receive mail using the email-check-exists processor. Returns the deliverability verdict for the address. Use it before adding a contact to a CRM or outreach list. Consumes credits per verification. ### Phone 1 - **Verify Phone** Check whether a phone number is valid and reachable using the phone-check-exists processor. Provide the number and its two-letter ISO country code for accurate line-type and validity detection. Consumes credits per verification. ### Enrichment 2 - **Get Gender by Name** Infer the likely gender for a given first name using the name-get-gender processor. Returns the predicted gender for the supplied name. Use it to enrich a contact record. Consumes credits per lookup. - **Company Search** Search for company records by name using the company-search-by-name processor. Provide the company name and a two-letter ISO country code to scope the search. Returns matching company data. Consumes credits per search. ### Catalog 2 - **List Groups** List the uProc tool groups, such as email, phone, company, communication, image, and text. Combine a group name with its tools to build a group-tool processor name for Run Tool. - **List Tools** List the tools (processors) available to your account, including each tool's name and expected parameters. Use a tool's name as the processor argument for Run Tool. Optionally filter to a single group. ### Account 1 - **Get Profile** Retrieve the authenticated account profile, including remaining credits. Use it as a connection check to confirm the email and API key are valid and to monitor the balance before running tools. ## Frequently Asked Questions ### What can FlowRunner do with uProc? FlowRunner agents can run Run Tool, Verify Email, and Verify Phone in uProc, plus 5 more actions. ### Does connecting uProc to FlowRunner require OAuth? No. uProc connects to FlowRunner with basic authentication (a username and password), no OAuth flow required. ### Can uProc trigger a FlowRunner workflow automatically? uProc doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at uProc?** This integration exposes uProc to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/uproc. Site index: https://flowrunner.ai/llms.txt