> ## Documentation Index > Fetch the complete documentation index at: https://rocketyard.dev/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > These Actors run on the Apify platform and charge per result. Call one with POST https://api.apify.com/v2/acts/rocketyard~/run-sync-get-dataset-items and the header Authorization: Bearer , or connect Apify's MCP server at https://mcp.apify.com?tools=rocketyard/. # Find companies by what their job descriptions say, without code > Use job descriptions as hiring signals for sales and account research: export Greenhouse, Lever and Ashby jobs and filter them in Sheets, Make or Zapier. Job descriptions say a lot about a company: the software it runs, the compliance work it's taking on, the teams it's building. If you do sales or account research, you can search them for the terms that matter to you, without writing code. ## What you get without code Greenhouse, Lever and Ashby publish free APIs, but those return raw data per company, and using them means writing code. The [Greenhouse](https://rocketyard.dev/greenhouse-jobs-scraper.md), [Lever](https://rocketyard.dev/lever-jobs-scraper.md) and [Ashby](https://rocketyard.dev/ashby-jobs-scraper.md) Actors on Apify add: * **No code**: fill in a form, click Start, and get a table. * **Exports**: download CSV or Excel for a spreadsheet, or send results through Make, Zapier or n8n. * **A schedule**: re-run weekly or daily, without a server. * **One format**: every job has the same columns on all three platforms, including `company`, `title`, `department`, `location`, `url` and a plain-text `description`. The raw APIs each name and format these differently. ## Why search descriptions, not titles Titles rarely name the tools. We searched 8,405 open jobs on 29 company boards on 2026-11-05, matching whole words and ignoring case: | Term | Jobs naming it in the description | In the title | Boards with at least one | | - | - | - | - | | Salesforce | 616 | 1 | 25 of 29 | | Kubernetes | 530 | 0 | 24 of 29 | | Terraform | 245 | 1 | 22 of 29 | | SOC 2 | 194 | 0 | 21 of 29 | | Workday | 151 | 8 | 21 of 29 | | Snowflake | 138 | 0 | 20 of 29 | | HubSpot | 31 | 0 | 13 of 29 | These are mentions, not proof of use. A company's own product or boilerplate counts too: every one of Vanta's 84 jobs mentions SOC 2, because Vanta sells SOC 2 compliance software. Read the sentence before you act on it. ## 1. List the companies The Actors read the boards you name; they don't discover companies. Start from your account list. The board name is often the company's name in lower case, and the address of a job on its careers page confirms it (`job-boards.greenhouse.io/figma`, `jobs.lever.co/zoox`, `jobs.ashbyhq.com/ramp`). You can also test guesses. A name without a board comes back as a free error item, so paste your guesses into **Job board names** and see which ones return jobs. ## 2. Run the Actor 1. Open the Actor for the platform, for example [Greenhouse](https://apify.com/rocketyard/greenhouse-jobs-scraper), and click **Try for free**. 2. Paste the board names into **Job board names**. 3. Optional: narrow by **Department** or **Location** to pay for fewer jobs. Leave **Keyword in job title** empty, because it reads titles and would drop the jobs you're looking for. 4. Click **Start**. ## 3. Find the term in the descriptions The Actors don't search descriptions themselves, so you do this step in the tool you already use. **Google Sheets.** Export the run as CSV, then use **File > Import** in Sheets. If `description` is column F, this keeps the matching rows: ```text theme={null} =FILTER(A2:Z, REGEXMATCH(F2:F, "(?i)salesforce")) ``` **Make.** 1. Apify: **Run an Actor**, with your input. Set **Run synchronously** to **Yes** for small runs. Make limits how long a synchronous run can take, depending on your plan, so use **Watch Actor Runs** as the trigger for larger ones. 2. Apify: **Get Dataset Items**, with the run's default dataset ID. 3. A filter on the route: `description`, **Contains (case insensitive)**, your term. 4. Google Sheets: **Add a Row**, mapping `company`, `title`, `location` and `url`. **Zapier.** 1. Trigger: Apify, **Finished Actor run**. Zapier stops synchronous runs after 30 seconds, so start with the trigger. 2. Apify: **Fetch dataset items**. 3. **Filter by Zapier**: `description` contains your term. 4. Google Sheets: **Create Spreadsheet Row**. Test this on a small board first, and check that each job arrives as its own row before you rely on it. **n8n.** Use a Schedule Trigger, then Apify's community node (**Run an Actor and get dataset**) or the HTTP Request workflow on the [Actor's page](https://rocketyard.dev/greenhouse-jobs-scraper.md#automation). Add a **Filter** node on `description`, then Google Sheets **Append Row**. ## 4. Keep it fresh Add an [Apify schedule](https://rocketyard.dev/track-new-jobs-daily.md#1-schedule-a-daily-run) to re-run weekly. Each run returns the jobs open that day. To see only what's new, compare runs by `jobId`. ## What it costs You pay per job stored, whether or not its description matches your term: $1.00 per 1,000 jobs on Greenhouse, $0.75 on Lever and $0.75 on Ashby, plus a small start fee per run. Figma's board had 145 jobs on 2026-11-05, so one run costs $0.14. Department and location filters reduce it. **Maximum cost per run** caps a run. The Actors return job postings only, with no data about applicants or recruiters. You're responsible for how you use the data under the applicable terms and the law. > [card] [Run Greenhouse Jobs API & Scraper on Apify](https://apify.com/rocketyard/greenhouse-jobs-scraper) > > \$1.00 per 1,000 jobs, no subscription. You run it with your own Apify account. > [card] [Run Lever Jobs API & Scraper on Apify](https://apify.com/rocketyard/lever-jobs-scraper) > > \$0.75 per 1,000 jobs, no subscription. You run it with your own Apify account. > [card] [Run Ashby Jobs API & Scraper on Apify](https://apify.com/rocketyard/ashby-jobs-scraper) > > \$0.75 per 1,000 jobs, no subscription. You run it with your own Apify account. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.