---
title: "Integrations - Enrow"
url: "https://docs.unified.to/integrations/enrow"
description: "Build Enrow integrations faster with our Unified API — Enrichment data, API key, real-time sync."
date: "2026-11-12T22:56:59.465Z"
updated: "2026-11-12T22:56:59.465Z"
---

# Enrow integration

> What this integration supports through the Unified.to API, by object. Live data: `GET https://api.unified.to/unified/integration?type=enrow` with your workspace API key (or Core MCP `list_unified_integrations` with `type: "enrow"`). All integrations: https://docs.unified.to/integrations.md

## Overview

- **Type:** `enrow`
- **Categories:** [Enrichment](https://docs.unified.to/enrich/overview.md), [Passthrough](https://docs.unified.to/passthrough/overview.md)
- **Website:** https://enrow.io
- **Vendor API docs:** https://docs.enrow.io/api-overview
- **Launched:** 2026-11-11

## How end users connect

- **API key** entered by the end user: `API Key`
    - Sign in at app.enrow.io and click API in the left menu.
    - Copy your API key.

## Supported objects

| Object | Methods | Webhooks |
| --- | --- | --- |
| [enrich_person](#enrich_person) | none | none |
| [passthrough](#passthrough) | none | none |

Values below come from the integration's support data. "Required list filters" must be sent on list calls; "Required on create" fields must be sent when creating. Webhook events are `native` (pushed by the vendor) or `virtual` (polled by Unified.to). Anything not listed is not supported; an unsupported method returns `501`.

### enrich_person

- **Methods:** none
- **Webhooks:** none
- **Readable fields:** `company`, `company_domain`, `emails`, `first_name`, `gender`, `id`, `last_name`, `linkedin_url`, `name`
- **Writable fields:** none
- **Vendor objects:** `email_result`
- **Model:** https://docs.unified.to/enrich/person/model.md

### passthrough

- **Methods:** none
- **Webhooks:** none
- **Readable fields:** none
- **Writable fields:** none