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

# Fetch Jobs

> Pull public job postings by company domain — ideal for spotting buying intent, prioritizing accounts, or personalizing outreach.

## What It Does

* **Fetches active and historical job listings** for a company using its domain
* **Returns title, description, posting URLs, and timestamps** for each job
* **Filters by timeframe** — last month, quarter, 6 months, or year
* **Fetches up to 10,000 job postings per company**
* **Preserves your original data** while appending one row per job
* **Auto-handles naming conflicts** (e.g., `title_1` if `title` exists already)

***

## 🏁 Getting Started

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

<Steps>
  <Step title="Add the Node">
    Drop **Fetch Jobs** anywhere in your flow — it’s ideal after enrichment.
  </Step>

  <Step title="Enter the Domain">
    Map or enter a domain — e.g., `nrev.ai`, or use `@domain` dynamically from earlier steps.
  </Step>

  <Step title="Set Timeframe and Limit">
    Choose how far back to look and how many jobs to fetch:

    * Timeframes: last **month**, **3 months**, **6 months**, or **year**
    * Limit: up to **10,000 jobs** via dropdown
  </Step>

  <Step title="Toggle Active Jobs Only">
    Choose whether to return **only live** roles or include historical ones too.
  </Step>

  <Step title="Run the Node">
    Each job becomes a new row — ready for scoring, tagging, or personalization.
  </Step>
</Steps>

***

## Inputs

### 🛠️ Required Fields

* **Company Domain (✅)**\
  Domain to fetch job data for (e.g., `nrev.ai`).\
  *Tip:* Use `@domain` to map dynamically from earlier steps.

* **Last Detected After (✅)**\
  Filter for recency. Options include:
  * `Last month`
  * `Last 3 months`
  * `Last 6 months`
  * `Last year`

* **Limit (✅)**\
  Max number of job listings per company:
  * `100`, `200`, `500`, `1000`, `2000`, `5000`, `10000`\
    *Tip:* Helps control data size and credit usage.

* **Active Jobs Only (✅)**\
  Toggle ON for only current jobs, or OFF to include historical listings.

<Note>
  All inputs are validated via dropdowns — no manual entry errors or over-limit issues.
</Note>

***

## Output

Returns a **job-level dataset** for each company — one row per job:

| Field            | Description                      |
| ---------------- | -------------------------------- |
| `title`          | Job title                        |
| `description`    | Job description text             |
| `posting_url`    | Link to the original job post    |
| `job_first_seen` | First date this job was detected |
| `job_last_seen`  | Most recent detection date       |

***

## How It Works

1. Reads the input domain (`nrev.ai`, or `@domain`)
2. Queries for active and/or historical jobs
3. Filters based on your timeframe + volume
4. Returns one row per job post
5. Appends clean, conflict-free data

***

## 🚀 Use Cases & Prompts

| Use Case                 | Setup Example                                                  |
| ------------------------ | -------------------------------------------------------------- |
| Hiring Signal Scoring    | Fetch jobs from `@domain`, score accounts hiring for GTM roles |
| Growth Intent Detection  | Filter for job activity in the last 3 months                   |
| Outbound Personalization | Use job descriptions to write tailored cold emails             |
| Market Mapping           | Compare hiring across industries or regions                    |

***

## ✨ Pro Tips

<Tip>
  Use **`@domain`** to fetch job data dynamically row-by-row.
</Tip>

<Tip>
  Job fields like `title` may conflict with inputs — we auto-resolve (e.g., `title_1`). You can clean this with a Rename node later.
</Tip>

<Tip>
  Looking for signs of growth?\
  Pair this node with **Enrich Company** or **Search People** to target hiring-stage accounts.
</Tip>

***

## ⚠️ Important Considerations

<Warning>
  If a domain is blank or invalid, no jobs will be fetched — the row stays intact.
</Warning>

<Warning>
  Duplicate domains = duplicate job rows. De-duplicate upstream if needed.
</Warning>

<Warning>
  Large fetches (e.g., 10k jobs) may take time — reduce the limit or filter timeframe if needed.
</Warning>

***

## 🛠 Troubleshooting & Gotchas

| Symptom              | Likely Cause                        | How to Fix It                             |
| -------------------- | ----------------------------------- | ----------------------------------------- |
| Blank job fields     | No jobs found or invalid domain     | Try expanding timeframe or check mapping  |
| `title_1` or similar | Field conflict with existing column | Use Rename node downstream                |
| Long run time        | Large limit selected                | Lower limit or break into smaller batches |

***

## 📝 FAQ

<AccordionGroup>
  <Accordion title="Can I fetch jobs dynamically per row?">
    Yes — use `@domain` to reference earlier rows. Each will fetch jobs for its own domain.
  </Accordion>

  <Accordion title="How far back can I look?">
    Up to 1 year. Choose from 1, 3, 6, or 12 months using the dropdown.
  </Accordion>

  <Accordion title="Is this only for live job postings?">
    By default, yes — but turn OFF **Active Jobs Only** to include historical roles.
  </Accordion>

  <Accordion title="What if no jobs are found?">
    You’ll get a blank row for that company — no credits charged.
  </Accordion>
</AccordionGroup>

***

## 💰 Pricing

| Action                | Credit Cost        |
| --------------------- | ------------------ |
| Per 100 jobs (1 page) | 2 credits per page |

<Note>
  Credits are calculated per 100 job rows returned.\
  Example: Limit 1000 → 10 pages → **20 credits**\
  No jobs = **no credits charged**
</Note>

***

<p style={{ fontSize: '1rem', fontWeight: 'bold', marginTop: '1.5rem' }}>
  Use hiring signals to time your outreach, target high-growth accounts, and connect when they’re building — not stalling. 📈🧠
</p>