Rodz has no native Salesforce destination, so use Make. Build a scenario that starts on a custom webhook, paste its URL as the webhookUrl of a Job Offers signal, then add Salesforce modules: search the account by domain, create or update it, create the hiring manager as a lead and a task carrying the job offer. Every matching offer costs 2 credits.
Key facts
A job offer costs 2 credits per lead, plus 0.5 credit per email found and 5 credits per phone found, charged on success only.
Without persona targeting, contact is "": the lead is the hiring company. With it, Rodz adds a decision-maker at that company.
A delivery that fails transiently (timeout or 5xx) is retried; a 4xx response is not.
Rodz identifies 400,000+ signals a month (July to September 2026 average).
Cost : 2 credits per lead (+0.5 credit per email found) Setup time : 30 min Salesforce connects through a Rodz webhook or the API (no native Rodz app)
Before you start
A Rodz account with credits (the test account includes 100) and an API key (Integrations → API).
A Make account and a Salesforce connection allowed to create accounts, leads and tasks.
Your job criteria: titles to include and exclude, description keywords, locations, company size.
Steps
Step 1.
Create the Make scenario and its webhook
In Make, create a scenario and pick the Webhooks → Custom webhook trigger. Add a webhook, name it (for example "Rodz job offers") and copy its URL. Make answers 200 on receipt, which is what Rodz expects.
Step 2.
Create the Job Offers signal with that URL
In Rodz, add the Job Offers signal and paste the Make URL in the webhook field. Filter on the titles that reveal your buyer’s need (for example "Account Executive", "Head of Sales" for a sales tool), company size and countries. With no location the search is worldwide: size the daily limit accordingly.
Turn on persona targeting if you want a decision-maker on top of the company. Keep the signal as a draft for now.
In the webhook module, click Redetermine data structure: Make waits for a first message. Send it from Rodz with POST /api/v1/signals/{signal_id}/test-webhook. Make then records the signal, contact and company fields. Right after, add a filter that stops messages where signal.is_test is true.
Send a test payload
curl -X POST "https://api.rodz.io/api/v1/signals/$SIGNAL_ID/test-webhook" \ -H "Authorization: Bearer $RODZ_API_KEY"
Step 4.
Create or update the Salesforce account
Add Salesforce → Search Records on the Account object, with a condition on the website (company.website). Follow it with a Router: when an account is found, Update a Record; otherwise, Create a Record (Account) with name, website, industry and headcount. The domain is the most reliable key against duplicate accounts.
Step 5.
Create the lead and the follow-up task
On the main route, add a filter "contact.email exists", then Create a Record on the Lead object (first name, last name, email, title, company). Finally add Create a Record on the Task object, related to the account, with the job title as subject and the offer link and date as description. Turn the scenario on, then set the Rodz signal to Active.
Example payload
What the Make webhook receives for one offer, with persona targeting on (without it, `contact` is `""`).
Salesforce’s Industry field is a picklist: when the Rodz industry is not in it, write it to a custom text field.
Why a job offer is a buying signal
A company hiring for a function is investing in that function: an open sales role announces a need for sales tools, a data engineer role a need for data. The Salesforce task gives the rep the exact context (the offer and its date) to open the conversation.
Make receives nothing: the scenario must be on (or listening during the test) and the URL in the signal must be the Make webhook URL.
Salesforce error on Industry: the value is not in the picklist; map it to a text field.
Leads without email: persona targeting or email finding is off, or no email was found (not charged). The filter in step 5 then avoids creating an empty lead.
Frequently asked questions
Does Rodz have a native Salesforce integration?
Not among Rodz’s public destinations (HubSpot, Pipedrive, Google Sheets, lemlist, custom webhook...). For Salesforce, Rodz sends each lead to a webhook: Make, as here, or your own receiver that calls the Salesforce API.
Does Make verify the Rodz HMAC signature?
Not with the standard Custom webhook module: it reads the JSON, not the raw bytes the signature is computed on. Keep the Make URL private. If every delivery must be verified, put the signed receiver from the HMAC webhook recipe in front; it then forwards to Make or Salesforce.
How do I avoid duplicate accounts in Salesforce?
Search the account by domain (company.website) before creating it, as in step 4. Rodz retries a failed delivery with the same X-Webhook-Id header: store it in a Make data store if you want to skip a second arrival.
Lead or Contact in Salesforce?
A Lead fits cold prospecting: it is converted later. If the company is already a managed account, create a Contact linked to the account found in step 4 instead. Both are Create a Record modules with a different object.
How many offers will I receive?
As many as your filters find, within the signal’s daily limit. Each offer delivered costs 2 credits. If volume is too low, the signal’s funnel (GET /api/v1/signals/{signal_id}/funnel) shows which filter removes the most offers.