> ## 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 Technologies

> Reveal what technologies a company is using based on its domain — great for GTM research, outreach personalization, or stack fit scoring.

## What It Does

* **Reveals detected technologies** used by a company (e.g., Salesforce, HubSpot, Segment)
* **Pulls stack data by domain** — no need to scrape, guess, or buy outdated lists
* **Filters by timeframe** — see recently detected vs. long-standing tools
* **Limits results via dropdown** — up to 10,000 technologies per company
* **Appends one row per tech** — your original data stays untouched
* **Auto-resolves column conflicts** — like `tech_title_1` if needed

***

## 🏁 Getting Started

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

<Steps>
  <Step title="Add the Node">
    Drop **Get Company Technologies** into your workflow.
  </Step>

  <Step title="Enter the Domain">
    Map or enter a domain (e.g. `nrev.ai`) — or use `@domain` to reference from earlier.
  </Step>

  <Step title="Set Timeframe and Limit">
    Filter by last seen: `Last month`, `3 months`, `6 months`, or `1 year`.\
    Pick a result limit — up to `10,000` per company.
  </Step>

  <Step title="Run the Node">
    Each detected technology becomes its own row, appended to your input data.
  </Step>
</Steps>

***

## Inputs

### 🛠️ Required Fields

* **Company Domain (✅)**\
  A valid domain like `nrev.ai`. Use `@domain` to map dynamically.\
  *Why it matters:* This is how we identify each company’s tech stack.

* **Last Detected After (✅)**\
  Timeframe selector:
  * `Last month`
  * `Last 3 months`
  * `Last 6 months`
  * `Last year`

* **Limit (✅)**\
  Choose how many tech rows to return per company:\
  `100`, `200`, `500`, `1000`, `2000`, `5000`, `10000`

<Note>All fields are dropdown-based — no typos, no invalid values.</Note>

***

## Output

Each row contains a technology detected for a given domain, along with the original data.

### 🔹 Returned Fields

* `tech_title` – Technology name (e.g. Segment)
* `tech_url` – Info link for the detected tech
* `first_seen_at` – Date the tech was first detected
* `last_seen_at` – Most recent detection date

***

## How It Works

1. Takes your domain(s) and time filters
2. Queries enrichment vendor (PredictLeads)
3. Returns one row per tech tool
4. Preserves your existing fields and columns
5. Handles conflicts with suffixes (`tech_title_1`, etc.)

***

## 🚀 Example Use Cases

| Use Case              | Prompt or Setup                               |
| --------------------- | --------------------------------------------- |
| Personalize outreach  | "Target companies using Segment + HubSpot"    |
| Stack-fit scoring     | "Prioritize leads using ZoomInfo + G2 + SFDC" |
| Segment by stack      | "Group accounts using Snowflake or dbt"       |
| Run competitor audits | "See what tools your top rivals are using"    |

***

## ✨ Pro Tips

<Tip>
  Use `@domain` to enrich per row — great for SDRs and GTM automation.
</Tip>

<Tip>
  Tech fields like `tech_title` may conflict with your schema — we auto-suffix them to avoid breaking downstream nodes.
</Tip>

<Tip>
  Pair this with **Search People** to pull contacts at tech-matched companies, or **CSV Write** to share filtered lists with AEs or partners.
</Tip>

***

## ⚠️ Considerations & Gotchas

<Warning>
  You’ll get **one row per technology** — large stacks = lots of rows.
</Warning>

<Warning>
  Blank or invalid domains are skipped — your play won’t fail.
</Warning>

<Warning>
  Column name conflicts are auto-suffixed (e.g. `tech_url_1`) — clean up with **Rename Column** if needed.
</Warning>

***

## 🛠 Troubleshooting

| Symptom                 | Cause                               | Quick Fix                               |
| ----------------------- | ----------------------------------- | --------------------------------------- |
| Blank rows              | Domain missing or no techs detected | Check mapping and adjust your timeframe |
| Too many rows           | One row per tech is expected        | Use filters or group downstream         |
| Unexpected column names | Conflict resolved by suffix         | Rename columns after run if needed      |

***

## 📝 FAQ

<AccordionGroup>
  <Accordion title="Where does the tech data come from?">
    We use **PredictLeads** as the current vendor. More sources coming soon.
  </Accordion>

  <Accordion title="Do I need to manually enter domains?">
    Nope! Use `@domain` to reference from upstream inputs like Enrich Company.
  </Accordion>

  <Accordion title="How recent is the tech info?">
    You control that with the **Last Detected** dropdown — up to 1 year ago.
  </Accordion>

  <Accordion title="Are credits charged if no tech is found?">
    No — enrichment is only charged when valid results are returned.
  </Accordion>
</AccordionGroup>

***

## 💰 Pricing

| Action           | Credit Cost                                  |
| ---------------- | -------------------------------------------- |
| Per page fetched | 2 credits × number of pages (1000 rows/page) |

<Note>Example: No techs = no charge.</Note>

***

<p style={{ fontSize: '1rem', fontWeight: 'bold', marginTop: '1.5rem' }}>
  Peek under the hood of any company. Whether you’re qualifying leads or building TAM lists, Get Company Technologies helps GTM teams move smarter. 🔍💼
</p>