No-Code Job Data Extraction: Indeed Listings to a Make Data Store
Job boards move fast, and checking each search page by hand does not scale. This walkthrough shows how to turn a Customer Service search on Indeed into a repeatable pipeline: a scraping API request pulls five fields from every listing, Make splits the results, and a data store keeps one row per job. The plan covers searching Customer Service roles across several cities, running the API call inside Make, saving results to a spreadsheet-style store, forwarding them by email or newsletter, raising an alert for new postings, and scheduling the scenario to run at least daily. The same structure adapts to other queries, industries or locations.
Why extract job data at all
Structured job data supports several practical tasks:
- Running a job board or newsletter that needs fresh postings.
- Tracking which companies are hiring and which roles are in demand.
- Comparing salary ranges across locations or industries.
- Researching career options before applying.
A scraping tool can gather listings from a category and export them as a spreadsheet, CSV or database. The workflow below focuses on Indeed search results for Customer Service roles, but the same structure applies to other queries and locations.
What you need before you start
You will need a scraping API account and a Make account. In this workflow, the scraping API issues the page request and applies extraction rules, while Make is the automation platform that connects the modules moving data between services. The API handles proxies and headless browsers so you can focus on extraction; this guide relies on that documented capability rather than restating it as a guarantee.
The API also offers JavaScript scenarios and screenshots, but neither is required here. The extraction rules are the core feature: they let you pull structured values from a page without parsing HTML yourself.
Choose the fields and selectors
The example target is the Indeed search page for Customer Service roles at https://uk.indeed.com/jobs?q=Customer%20Service. The fields captured are job title, link, company name, company location and salary. You can add more, such as a job summary or rating, if your use case needs them.
The general form of an extraction rule is a key name paired with a CSS selector. Because every listing on the page shares the same HTML structure, one set of rules can run across all of them. To return every matching element rather than a single result, use the list type.
The extraction rules
The complete extraction rules for this workflow are supplied as a protected module and appear in full alongside this page. They define a results selector, a list type, and output keys for link, title, name, location and salary. The link key uses an @href output so the anchor target is captured rather than its text.
When the rules run against the Customer Service search page, the output is a list of records. A representative record from the captured example looks like this: a link beginning /rc/clk?jk=..., the title Customer Service Advisor, the company City of Westminster Council, the location Westminster, and the salary £27,009 - £30,063 a year. That record is the sample used later to build the data store structure.
Test the request in the scraping API dashboard
Before wiring anything into Make, test the call in the scraping API dashboard Request Builder. Enter the Indeed URL in the URL field, leave JavaScript rendering off, tick the extract rules box, paste the rules, and click Try it. Rendering JavaScript with a headless browser is billed at 5 credits per request under the API's documented credit model; confirm the current figure in the API's own pricing documentation before budgeting. If the preview returns the five fields for each listing, the rules are ready to reuse in the automation.
Obtain your API key from the dashboard and copy it for the Make connection step.
Set up the Make scenario
Create a new scenario in Make and add a scraping API module as the first step. Choose the Make an API call action. Make uses connections to link services that require authentication, so add a new connection and paste the API key when prompted.
In the action configuration, set the method to GET. Enter the Indeed job listing URL in the URL field. Open Show advanced settings and paste the extraction rules into the Extract Rules (JSON) field. Set Render JS to No, since this job does not need it and it costs extra credits. Use Run Once to test the module before continuing.
Split the results with an Iterator
The scraping API module returns one bundle containing a list of listings. The next module, an Iterator under Flow Control, takes that single bundle and emits one bundle per listing, so each job can be handled on its own. Configure the Iterator to use Body → Results.
This matters because the following module writes one record per listing. Without the Iterator, the data store would receive the whole list as a single item rather than one row per job.
Create the data store and its structure
Add a Data store module and choose Add/replace a record. If you do not already have a data store, create one and give it a name such as Indeed jobs. A data structure is the schema that lists each column name and its data type. You can add columns one at a time with Add item, or let the Generator infer them from a sample record.
For this workflow, the sample record produces five columns: link, title, name, location and salary. If you leave the data structure field empty, the store will contain only the primary key, so selecting or creating a structure is essential for storing the job fields.
Map the record fields
In the Add/replace a record action, set a unique Key if you want to retrieve the record later; leaving it blank lets Make generate one. Enable Overwrite an existing record only if you intend to replace a record with the same key. With overwrite disabled, submitting a key that already exists in the store causes the module to fail rather than silently duplicate the row.
Map Title, Link, Name, Salary and Location from the Iterator output into the matching record fields. When building the link value, prefix it with https://uk.indeed.com and no space or trailing slash before the path, so the stored URL is correctly formed. Run the scenario again and expand the results to confirm each listing became its own record.
Send the data onward and schedule the run
Once records are stored, you can route them to other modules. A router lets you split the flow into multiple paths, and each path can have its own filter. Common destinations include Slack notifications, email, an email marketing campaign, or a CMS item. A filter such as 'salary is present' is a simple way to keep only listings with pay information.
To run the scenario automatically, open the Schedule tab, click the clock icon on the scraping API module, and set the interval and start time. The example uses 60 minutes. Automatic runs only happen when scheduling is switched on for the scenario; the interval and start time alone will not trigger anything.
Recap of the workflow
The scenario has four parts: a scraping API Make an API call that fetches and extracts the listings, an Iterator that splits the results, a Data store Add/replace a record that saves each listing, and a router that forwards records to destinations such as Slack, Mailchimp or email. With the schedule enabled, the pipeline can refresh on its own instead of requiring manual page reads.
| Extracted key | Source on the listing | Data store column | Note |
|---|---|---|---|
| title | h2.jobTitle>span | title | Job title text |
| link | a.tapItem... @href | link | Prefix with https://uk.indeed.com, no space or trailing slash |
| name | span.companyName | name | Company name |
| location | div.companyLocation | location | Company location |
| salary | div.salary-snippet | salary | May be absent on some listings |
Selectors and field names reflect the example; page structure can change, so verify selectors against the current page before relying on them.
| Check | Why it matters |
|---|---|
| JavaScript rendering is off | Rendering costs extra credits under the API's documented model and is not needed for this extraction |
| Extract rules return a list | A single result would store only one listing |
| Iterator uses Body → Results | Each listing must become its own bundle |
| Data structure has five columns | An empty structure stores only the primary key |
| Overwrite setting matches your intent | Duplicate keys error when overwrite is disabled |
| Link prefix is correct | Missing prefix produces malformed URLs |
| Scheduling is turned on | Settings alone do not trigger automatic runs |
Checklist derived from the workflow steps; confirm current platform behaviour before production use.
Frequently asked questions
Do I need JavaScript rendering to extract Indeed job listings?
No. This workflow turns JavaScript rendering off because it is not required for this extraction, and rendering with a headless browser costs extra credits under the API's documented model.
Why does the data store need an Iterator?
The scraping API call returns one bundle containing all listings. The Iterator splits that bundle so each listing is written as a separate record instead of the whole list being stored as one item.
What happens if I add a record that already exists?
If Overwrite an existing record is disabled and you try to add a record under the same key, the module throws an error. Enable overwrite if you intend to replace existing records.
Why does the stored link need a prefix?
The extracted link is a relative path. Adding https://uk.indeed.com with no space or trailing slash before it produces a correctly formatted absolute URL.
{
"results": {
"selector": "a.tapItem.fs-unmask.result.resultWithShelf.sponTapItem.desktop",
"type": "list",
"output": {
"link": {
"selector": "a.tapItem.fs-unmask.result.resultWithShelf.sponTapItem.desktop",
"output": "@href"
},
"title": "h2.jobTitle>span",
"name": "span.companyName",
"location": "div.companyLocation",
"salary": "div.salary-snippet"
}
}
}
"link": "/rc/clk?jk=0d5c8c0dfe43c3d5&fccid=057e594637329eab&vjs=3",
"title": "Customer Service Advisor",
"name": "City of Westminster Council",
"location": "Westminster",
"salary": "£27,009 - £30,063 a year"
{
"results": {
"selector": "a.tapItem.fs-unmask.result.resultWithShelf.sponTapItem.desktop",
"type": "list",
"output": {
"link": {
"selector": "a.tapItem.fs-unmask.result.resultWithShelf.sponTapItem.desktop",
"output": "@href"
},
"title": "h2.jobTitle>span",
"name": "span.companyName",
"location": "div.companyLocation",
"salary": "div.salary-snippet"
}
}
}
{
"link": "/rc/clk?jk=0d5c8c0dfe43c3d5&fccid=057e594637329eab&vjs=3",
"title": "Customer Service Advisor",
"name": "City of Westminster Council",
"location": "Westminster",
"salary": "£27,009 - £30,063 a year"
}