# How do you send companies that are hiring to Pipedrive?

> Source: https://www.rodz.io/en/guides/use-cases/job-offers-to-pipedrive/
> Updated on 2026-10-12 · Peter Cools · Recipe · Job offers (hiring) · Pipedrive

## Short answer

Create a Job Offers signal in Rodz with the job titles that reveal a need, the job location and the company size, then switch on Pipedrive in the signal’s Integrations tab. Every company that is hiring lands in Pipedrive as an organization, with a note describing the job offer. Turn on persona targeting to get the decision-maker too. A lead costs 2 credits.

## Key facts

- A job offer costs **2 credits** per lead, plus 0.5 credit per email found, charged on success only.
- The first run looks back **7 days** by default (`publishedDate`); after that the signal follows offers published in the last 7 days.
- A company is delivered **at most once a day**, however many jobs it posts.
- Rodz identifies **400,000+ signals a month** (July to September 2026 average).

Cost: 2 credits per lead (+0.5 credit per email found)

## Before you start

- A Rodz account with credits (the test account includes 100).
- A Pipedrive account where you can authorize an app.
- The job titles that signal a need for your offer (for example "Account Executive" if you sell a tool to sales teams).

## Steps

### 1. Connect Pipedrive to Rodz

In the Rodz dashboard, open **Integrations** and click **Pipedrive**. Allow access in the Pipedrive window. You connect once for the account; the API cannot connect Pipedrive (`PUT /api/v1/integrations/pipedrive` answers `USE_DASHBOARD_OAUTH`).

### 2. Create the Job Offers signal

In **My Signals**, click **Activate Signal** and pick **Job Offers** and set:

- the **titles to include** (`jobTitleInclude`) and to exclude (`jobTitleExclude`, for example "Intern");
- **description keywords** when the title is not enough (`jobDescriptionInclude`);
- the **job location** (`locations`): where the job is, not the headquarters. Empty means worldwide;
- the **company size**. Staffing and consulting firms are excluded by default (`companyIndustryExcluded`).

`Equivalent configuration (body of POST /api/v1/signals/job-offers)`

```json
{
  "name": "Sales teams that are hiring",
  "dailyLeadLimit": 20,
  "status": "draft",
  "config": {
    "jobTitleInclude": ["Account Executive", "Business Developer"],
    "jobTitleExclude": ["Intern", "Internship"],
    "locations": ["France"],
    "companySizeFilters": ["51-200", "201-500"],
    "publishedDate": "7d",
    "enablePersonaTargeting": true,
    "targetPersonas": ["Sales Director"],
    "maxLeadsPerCompany": 1,
    "getEmails": true
  }
}
```

### 3. Choose company only or decision-maker

Without persona targeting, each lead is a **company**: Pipedrive gets the organization and a note. With targeting (for example "Sales Director"), Rodz adds the decision-maker as a person linked to the organization. `maxLeadsPerCompany` sets the number of contacts per company per day.

Note: on this signal the **daily limit counts companies**. A limit of 20 with 2 contacts per company can deliver up to 40 leads.

### 4. Switch on Pipedrive for this signal

In the signal’s **Integrations** tab, switch on **Pipedrive** and save. Through the API: `PATCH /api/v1/signals/{signal_id}` with the `pipedrive` destination.

`Same setting through the API`

```bash
curl -X PATCH "https://api.rodz.io/api/v1/signals/$SIGNAL_ID" \
  -H "Authorization: Bearer $RODZ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"destinations": {"pipedrive": {"enabled": true}}, "status": "active"}'
```

### 5. Check the first organizations

Once the signal is **Active**, open Pipedrive: the organizations created or updated carry a note with the job title, its link and its publication date. On the Rodz side, `GET /api/v1/signals/{signal_id}/leads` returns the same leads.

## Example payload

What Rodz delivers for one job offer (webhook format, also returned by `GET /api/v1/signals/{signal_id}/leads`). `contact` is `""` without persona targeting.

```json
{
  "signal": {
    "id": "f6a7b8c9-d0e1-4f2a-b3c4-d5e6f7a8b9c0",
    "name": "Sales teams that are hiring",
    "type": "job_offers",
    "last_signal": "Job Offer",
    "last_signal_date": "2026-10-09",
    "job_offer_url": "https://careers.example/northwind/account-executive",
    "job_offer_title": "Mid-Market Account Executive",
    "job_offer_location": "Lyon (France)",
    "job_offer_description": "We are hiring an Account Executive to grow our mid-market portfolio...",
    "job_offer_date": "2026-10-08",
    "job_offer_published_date": "2026-10-08",
    "job_offer_source": "LinkedIn",
    "matched_keywords": "Account Executive"
  },
  "contact": {
    "lead_id": "a7b8c9d0-e1f2-3456-7890-abcdef012345",
    "created_at": "2026-10-09T06:30:00+00:00",
    "first_name": "Sophie",
    "last_name": "Moreau",
    "email": "sophie.moreau@northwind.example",
    "phone": "",
    "title": "Sales Director",
    "location": "Lyon, Auvergne-Rhône-Alpes, France",
    "country_code": "FR",
    "city": "Lyon",
    "linkedin_profile_url": "https://www.linkedin.com/in/sophie-moreau-example",
    "sales_navigator_profile_url": "",
    "matched_persona": "Sales Director"
  },
  "company": {
    "name": "Northwind Software",
    "website": "https://northwind.example",
    "linkedin_url": "https://www.linkedin.com/company/northwind-software-example",
    "industry": "Software Development",
    "employee_count": 180,
    "employee_range": "51-200",
    "hq_country_code": "FR",
    "hq_city": "Lyon"
  }
}
```

## Rodz → Pipedrive field mapping

| Rodz field (payload)                                                 | Pipedrive object          | Where               |
| -------------------------------------------------------------------- | ------------------------- | ------------------- |
| `company.name`, `company.website`                                    | Organization              | Name, website       |
| `company.linkedin_url`, `company.industry`, `company.employee_count` | Organization              | Organization fields |
| `signal.job_offer_title`, `signal.job_offer_url`                     | Organization (and person) | "Job offer" note    |
| `signal.job_offer_location`, `signal.job_offer_published_date`       | Organization (and person) | "Job offer" note    |
| `contact.first_name`, `contact.last_name`                            | Person                    | Name                |
| `contact.email`, `contact.phone`                                     | Person                    | Email, phone        |
| `contact.title`                                                      | Person                    | Job title           |

The person is linked to the organization. Without persona targeting, only the organization and its note are created.

## A job offer is a budget

A company hiring for a function is investing in that function. If you sell to sales teams, an Account Executive opening announces a need for tooling and onboarding; if you sell recruiting, it is the demand itself. In Pipedrive, filter the organizations Rodz created and turn the ones that fit your ICP into deals.

For Salesforce, which has no native Rodz connection, see the [job offers to Salesforce with Make](/en/guides/use-cases/job-offers-to-salesforce-with-make/) recipe.

## Troubleshooting

- **No organization**: check that Pipedrive is switched on in the _signal’s_ Integrations tab and that the signal is Active.
- **Too many off-target companies**: tighten the titles, add exclusions or description keywords, narrow `locations`.
- **Organizations without a person**: persona targeting is off, or no decision-maker matches. Turn on `companyOnlyWhenContactsRefused` to keep the company even when your filters removed every contact.

## Frequently asked questions

### Does Rodz create a Pipedrive deal or lead?

No. Rodz creates or updates the organization, the person when a decision-maker is delivered, and adds a note with the job offer context. Creating deals stays in your hands, for example with a Pipedrive automation.

### Does a company posting ten jobs create ten leads?

No. A company is delivered at most once a day, however many jobs it posts. The next day, a new job can deliver it again depending on the signal’s duplicate handling.

### Why are staffing firms excluded?

They post jobs for their clients: the company hiring is not the one posting. `companyIndustryExcluded` excludes "Staffing and Recruiting" and "Business Consulting and Services" by default. You can change that list.

### How do I target a need rather than a job?

Combine the title and the description. A payroll software company will look for "Payroll Manager" offers; a data tool, for offers whose description names a specific tool (`jobDescriptionInclude`).

### Can I get older job offers?

Yes, on the first run only: `publishedDate` (for example `30d` or `3m`) sets how far back the first search goes. After that the signal follows offers from the last 7 days.

## Sources

- [Rodz API reference: create a Job Offers signal](https://api.rodz.io/docs)
- [Pipedrive Knowledge Base](https://support.pipedrive.com/)

## Related guides

- https://www.rodz.io/en/guides/use-cases/job-offers-to-salesforce-with-make/
- https://www.rodz.io/en/guides/use-cases/job-changes-to-hubspot/
- https://www.rodz.io/en/guides/api/poll-signal-leads/