Doing Good Leeds Jobs Scraper - Charity and Third-Sector Vacancies

Collect public charity, nonprofit, community, and third-sector vacancies from Doing Good Leeds in a structured Apify dataset. The Actor returns the job title, organization, location, employment type, public salary text, added date, closing date, vacancy URL, organization logo, source URL, and collection timestamp from the site's public job cards.

This Actor is designed for local job alerts, nonprofit recruitment research, regional labor-market analysis, vacancy aggregation, and recurring third-sector hiring feeds. It uses the server-rendered public jobs page, requires no account or external API key, and exports results to JSON, CSV, Excel, XML, RSS, or the standard Apify API.

What this Actor returns

Each default-dataset item is one public vacancy card with clear source provenance:

• title: the displayed job title;
• organization: the hiring charity, community group, or organization;
• location: the public location label, such as Leeds or West Yorkshire;
• employment_type: the displayed full-time or part-time label;
• salary_text: the published salary or See details when the card does not contain a numeric amount;
• added_text: the date text shown after ADDED;
• closing_text: the application-closing date text;
• url: the direct public vacancy page;
• organization_logo: the public logo image when the card includes one;
• search_url: the search page that produced the result;
• source: Doing Good Leeds;
• scraped_at: the UTC timestamp of collection.

The Actor does not invent normalized salaries or dates when the source provides only display text. This preserves fidelity and avoids false precision.

Use cases

Daily local job alerts

Run the Actor each morning, compare vacancy URLs against the previous dataset, and send only newly seen roles to email, Slack, Telegram, or a spreadsheet. The closing-date field helps recipients prioritize applications.

Charity and nonprofit job aggregation

Add Leeds and Yorkshire third-sector vacancies to a broader jobs product while retaining the original source and direct application page. Use the URL as the primary deduplication key.

Hiring-signal research

Track which local organizations are recruiting, the kinds of roles advertised, and the locations or employment types shown publicly. This can support nonprofit ecosystem research, workforce planning, or market reports.

Recruitment operations

Import current vacancies into an internal review sheet or database. Filter on organization, location, employment type, salary text, or closing date before a human decides which roles are relevant.

Historical vacancy monitoring

Schedule regular runs and retain snapshots to build a first-seen/last-seen history downstream. The Actor reports the current page; it does not claim that an absent card has been filled rather than removed or expired.

Input

The default input points to Doing Good Leeds' public job search and returns no more than ten records for a quick first run.

{
  "searchUrls": ["https://doinggoodleeds.org.uk/search-jobs/"],
  "maxResults": 10
}

Input fields

• searchUrls: one or more public Doing Good Leeds job-search URLs. If the site exposes filters in the URL, configure them in the browser and paste the result. Up to 20 URLs are processed in one run.
• maxResults: maximum unique vacancies stored for each input URL, from 1 to 100. The source can return fewer rows than requested.

For clean recurring workflows, save one Apify task per distinct audience or filter rather than combining unrelated searches.

Example output

{
  "title": "Community Development Worker",
  "organization": "Leeds GATE",
  "location": "West Yorkshire",
  "employment_type": "Full Time",
  "salary_text": "£27,097",
  "added_text": "11 June",
  "closing_text": "10 July",
  "url": "https://doinggoodleeds.org.uk/job/community-development-worker-11/",
  "organization_logo": "https://cdn-doinggood.b-cdn.net/example-logo.png",
  "search_url": "https://doinggoodleeds.org.uk/search-jobs/",
  "source": "Doing Good Leeds",
  "scraped_at": "2026-07-10T12:00:00+00:00"
}

Example values illustrate the schema. Live titles, organizations, salary text, dates, and URLs change as vacancies are added or closed.

Pricing and cost control

The Actor uses pay per event pricing:

• a small Actor-start event is charged once when a run begins;
• the result event is charged for each vacancy written to the default dataset.

The maxResults input provides a visible result ceiling. If one URL has a limit of 10, no more than ten unique vacancy rows from that URL are stored. Duplicate vacancy URLs across supplied searches are written only once per run. Apify platform usage is displayed separately.

Run through the API

curl -X POST \
  "https://api.apify.com/v2/acts/benthepythondev~doinggoodleeds-jobs-scraper/runs?token=$APIFY_TOKEN" \
  -H "content-type: application/json" \
  -d '{"searchUrls":["https://doinggoodleeds.org.uk/search-jobs/"],"maxResults":10}'

Keep the API token out of code repositories. The run response includes links to the default dataset, and the Actor works with standard Apify tasks, schedules, webhooks, and integrations.

Automation ideas

• Run every weekday and append only unseen vacancy URLs to Google Sheets.
• Notify a Slack or Telegram channel when a matching title appears.
• Filter by closing-date text before sending a daily email digest.
• Combine this source with StepStone, XING, InfoJobs, or ATS feeds in a normalized regional hiring pipeline.
• Track organization hiring frequency in a private research database.
• Archive monthly datasets for nonprofit labor-market analysis.

When parsing display dates downstream, add the appropriate year and timezone carefully. A card can omit the year because the website displays it in current page context.

Reliability and data quality

Doing Good Leeds currently serves semantic, server-rendered job-card elements. The Actor parses those cards directly, retries transient request failures, deduplicates vacancy URLs, and fails when the page contains no usable jobs. This explicit failure prevents a redesigned or blocked source from appearing healthy with an empty dataset.

The default input is small enough for Apify's routine testing and normal interactive use. The output schema and dataset view keep the Actor useful for both human inspection and agent/API workflows. Because the source is operated by a third party, page structure, vacancy availability, and access behavior can change without notice.

Responsible use

Use public vacancy data for legitimate job discovery, aggregation, research, or internal operations. Keep direct source links and verify important details on the original vacancy page before applying, publishing, or making decisions. Respect the source's terms, applicable copyright, privacy, employment, and database rules. Do not use organization or applicant data for harassment, discrimination, or unsolicited bulk messaging.

The Actor collects public job cards only. It does not submit applications, collect applicant data, access employer accounts, or bypass logins.

Limitations

• The Actor returns the public search-card fields, not every detail on each job page.
• Salary can be descriptive or See details; no numeric salary is fabricated.
• Display dates may omit a year and are therefore preserved as source text.
• A missing card can mean expiration, removal, a changed filter, or a source issue; downstream history should not assume the reason.
• Logo URLs remain controlled by the source CDN.
• The public page can contain fewer jobs than the configured result maximum.

Frequently asked questions

Does this require a Doing Good Leeds account?

No. The Actor reads public vacancy cards without logging in.

Can I collect only a few jobs for testing?

Yes. Set maxResults to 1, 2, or another small value. The default is 10.

Does it include the application deadline?

It returns the public closing_text shown on the card. Verify the final deadline and application instructions on the linked vacancy page.

Can it normalize salary to a number?

Not safely for every listing. Some cards show a numeric salary while others show See details. The Actor preserves the source text so a downstream process can apply rules appropriate to its use case.

Can I schedule daily alerts?

Yes. Save the input as an Apify task, schedule it, and trigger a webhook or integration when the run finishes. Deduplicate alerts by vacancy URL.

What should I include in a support issue?

Share the run ID, non-secret input URL, expected job title, and the incorrect or missing field. Never share an API token in a public issue.

Related Actors

• Remote Jobs Aggregator for multi-source remote vacancies.
• StepStone Scraper for European job-board research.
• XING Jobs Scraper for public DACH job listings.
• InfoJobs Jobs Scraper for public Spanish job listings.

If this Actor provides useful data, a short honest Store review helps other users evaluate it. Reproducible issues receive faster support when the report includes a run ID and the exact non-secret search URL.

Keywords: Doing Good Leeds scraper, Doing Good Leeds jobs API, Leeds charity jobs scraper, Yorkshire nonprofit vacancies, third sector jobs data, community jobs feed, charity recruitment API, UK nonprofit jobs, Apify jobs Actor.