> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nrev.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Get Company Partners

> Enrich your company data with partner relationships to map ecosystems, enhance intelligence, and power GTM insights.

## What It Does

* Retrieves partner relationships for a target company domain and outputs normalized partner data.
* Preserves all input columns while adding partner-specific columns (`partner_name`, `partner_domain`, `source_url`, `first_seen_at`, `last_seen_at`).
* Supports template variables for dynamic domain resolution per row (e.g., `@company_domain`).
* Automatically resolves column name conflicts with numeric suffixes to avoid overwriting existing data.
* Test mode fetches a single page for fast validation before running full-scale enrichment.

***

## 🏁 Getting Started

<Frame>
  <img src="https://mintlify.s3.us-west-1.amazonaws.com/nurturev/images/Get%20Company%20Partners%20config%20screenshot.png" alt="Get Company Partners config screenshot" style={{ borderRadius: '0.5rem', width: '100%', margin: '1.5rem 0' }} />
</Frame>

<Steps>
  <Step title="Select Vendor">Choose `predictleads` as your vendor source (currently the only option).</Step>
  <Step title="Set Company Domain">Enter a static domain (e.g., `microsoft.com`) or use `@ColumnName` for dynamic row-based resolution.</Step>
  <Step title="Configure Limit">Optionally set the maximum number of partner records to fetch. Pagination is handled automatically.</Step>
  <Step title="Connect Input (Optional)">Attach a previous node if using template variables, so `company_domain` can be resolved per row.</Step>
  <Step title="Run Node">Execute in Test Mode first to preview results, then Standard Mode for full enrichment.</Step>
</Steps>

***

## Inputs

### 🛠️ Required Fields

* **Company Domain (✅)**\
  The domain or URL of the target company (e.g., `microsoft.com` or `https://www.microsoft.com`).\
  *Why it matters:* Determines which company's partners are retrieved; supports per-row dynamic resolution with `@ColumnName`.

### 🎯 Optional Fields

* **Limit (⚪️)**\
  Maximum number of partner records to fetch.\
  *Why it matters:* Controls data volume and credit usage while ensuring you capture relevant relationships.

***

## Output

* Adds the following partner columns to your dataset:\
  `partner_name`, `partner_domain`, `source_url`, `first_seen_at`, `last_seen_at`
* Preserves all original input columns.
* Column name conflicts are resolved with numeric suffixes (e.g., `partner_name` → `partner_name_1`).

<Note>
  ✨ If any partner column name conflicts with your input, a numeric suffix is added automatically to preserve all data.
</Note>

***

## How It Works

1. Validate settings and placeholders (`company_domain` must be non-empty or a valid column reference).
2. Load input data if template variables are used.
3. For each row (or static domain), fetch partner relationships from PredictLeads using pagination.
4. Normalize partner data to standard columns (`partner_name`, `partner_domain`, `source_url`, `first_seen_at`, `last_seen_at`).
5. Merge partner data with input columns, resolving any conflicts with suffixes.

***

## 🚀 Example Use Cases & Prompts

| Use Case                 | Setup or Prompt Example                                              |
| ------------------------ | -------------------------------------------------------------------- |
| Map partner ecosystem    | Fetch partners for `microsoft.com` to understand alliances           |
| Competitive intelligence | Use `@company_domain` column to enrich competitor list with partners |
| Data enrichment          | Add partner relationships to your CRM dataset for richer insights    |

***

## ✨ Pro Tips

<Tip>
  * Run in **Test Mode** first to quickly preview a single page of partner data without consuming extra credits.
  * Rename output columns if you plan to join with other datasets (`PartnerName`, `PartnerDomain`) for clearer reports.
  * For multiple rows, use `@company_domain` via the Insert Input button to dynamically resolve domains per row.
</Tip>

***

## ⚠️ Important Considerations

<Warning>
  * Pagination consumes credits per page. Large limits in Standard Mode will use more credits.
  * Invalid or empty static/template domains will fail validation.
  * Column conflicts are resolved automatically, but review names to ensure consistency in downstream workflows.
</Warning>

***

## 🛠 Troubleshooting & Gotchas

| Symptom                  | Likely Cause                       | Quick Fix                                       |
| ------------------------ | ---------------------------------- | ----------------------------------------------- |
| Blank output             | No valid `company_domain` provided | Verify static domain or input column references |
| Unexpected `_1` suffixes | Column name conflicts with input   | Rename outputs for clarity                      |

***

## 📝 FAQ

<AccordionGroup>
  <Accordion title="Can I fetch partners for multiple companies at once?">
    Yes — use a column with domains (`@company_domain`) as input, and the node will resolve each row dynamically.
  </Accordion>

  <Accordion title="What if a column already exists in my input?">
    Partner columns will automatically receive a numeric suffix to avoid overwriting.
  </Accordion>

  <Accordion title="How does Test Mode differ from Standard Mode?">
    Test Mode fetches only a single page of results, making it faster and cheaper for validation.
  </Accordion>
</AccordionGroup>

***

## 💰 Pricing

| Action                  | Credit Cost       |
| ----------------------- | ----------------- |
| Row-level partner fetch | 1 credit per page |

<Note>
  Credits are consumed per page of results fetched. Using Test Mode helps limit consumption while testing.
</Note>

***

<p style={{ fontSize: '1rem', fontWeight: 'bold', marginTop: '1.5rem' }}>
  Drop this node into your Play to enrich company datasets with partner insights—automatically. 🚀
</p>