# Daily job-board hiring signals into HubSpot and Slack

> Every weekday at 8am, scan public job boards for fresh postings that match your ICP, log net-new HubSpot accounts with a hiring signal, and post one Slack digest.

- Workflow type: agent
- Services: RapidAPI, HubSpot, Slack
- Categories: Sales
- Published: 2026-07-02

## What it does

- Watches public job boards every weekday morning for postings from the last 24 hours that match your target roles, industries, and geographies.
- Filters out contractor gigs and backfill listings so only postings that suggest real budget or team scaling get flagged.
- Adds a hiring-signal flag on the matching HubSpot company, and creates a fresh company record if the account is not in your CRM yet.
- Queues a HubSpot task for the account owner with the role, the posting link, and a one-line reason the signal matters.
- Wraps up with a single Slack message that groups the day's signals by ICP tier so your SDR team knows where to focus first.

## What you'll need

- A RapidAPI account with an active subscription to a jobs search API in the RapidAPI Hub.
- A HubSpot login with access to companies, owners, and tasks.
- A Slack workspace and the channel where you want the morning digest to land.
- A short description of your ICP: target job titles, industries, countries, and whether you care about remote or onsite roles.

## Prompt

Build me an agent workflow that scouts fresh hiring signals off public job boards every weekday morning and pushes the strongest ones into HubSpot and Slack. It should run on a cron schedule, every weekday at 8am in my local time zone.

Step 1. Call the JSearch API on the RapidAPI Hub using RapidAPI Call a Subscribed Hub API. Hit the /search-v2 endpoint on jsearch.p.rapidapi.com with my ICP filters as query params: target role keywords (for example VP of Sales, Head of Data, RevOps Manager), country, remote_jobs_only where relevant, and date_posted set to today so we only see postings from the last 24 hours. Paginate through the cursor until there are no more results. Collect job title, employer_name, employer_website, employer_logo, job_country, job_city, job_apply_link, job_posted_at_datetime_utc, and job_description.

Step 2. Reason over each posting to decide if it's a real buying signal or noise. Skip contractor and temp listings, staffing-agency reposts, and same-title backfill roles. Keep postings that suggest scaling or new-function build-out: sales and SDR clusters, senior leadership reqs (VP, Head of, Director), first-of-role hires, ML or AI initiatives, or expansion into a new city or country. Group the surviving postings by employer_website domain.

Step 3. For each candidate company, call HubSpot Search Companies filtered by the domain to see if the account already exists. Capture the HubSpot company id, the account owner (owner id and email), and the last activity date. If nothing matches, mark the company as net-new.

Step 4. For every net-new company, call HubSpot Create Company with name, domain, industry (inferred from the posting when we can), country, and city. Then for both existing and net-new companies, call HubSpot Update Company to set an active_hiring_signal property with today's date and the top role title. If the property does not yet exist in the tenant, prompt me at setup so I can create it in HubSpot.

Step 5. For every company that made the cut, call HubSpot Create Task on the company record. The task title should include the job title and a short pain-point hook (for example: 'New SDR hire indicates scaling outbound' or 'First Head of Data suggests analytics buildout'). Task body includes the full posting URL, employer city and country, and a one-line 'why now' rationale. Assign the task to the existing account owner when one exists, or to a default rep I configure when the company is brand new. Set the due date to today.

Step 6. Rank the companies into ICP tiers based on signal strength: Tier 1 for multi-req sales or leadership build-outs at strongly-fit companies, Tier 2 for single strong-signal roles, Tier 3 for lighter-weight signals that are still worth a look. For each company draft a one-line 'why now' hook the SDR can use as a talking point.

Step 7. Post one consolidated digest to my SDR Slack channel using Slack Send a Message. Header: today's date and the total signal count. Then a section per ICP tier, and within each tier a compact block per company with the company name, the strongest role title, the one-line hook, and links to the HubSpot company record and the underlying posting. Keep the digest scannable even if the raw job feed was huge, aim for under 20 companies total across all tiers, and if nothing meets the bar today post a single short message saying so instead of padding.

Rules. Never post duplicate digest entries for the same company on the same day. Do not create tasks or update companies for postings that failed the noise filter. Keep Slack formatting in mrkdwn (single asterisks for bold, angle-bracket links). Use judgement, don't dump the raw JSearch payload into HubSpot notes.

Configurable inputs I should be prompted for at setup: the Slack channel for the digest, the local time zone for the 8am run, the ICP filters (target job title keywords, industries, countries, remote or onsite), the HubSpot default owner for net-new companies, and the skip phrases for the noise filter.

## How to customize

- Tune the ICP filters. Change target job titles, industries, countries, or the remote versus onsite mix.
- Adjust the schedule. Move it off 8am, run it three days a week instead of every weekday, or align it to your team's time zone.
- Change the destination. Send the digest to a different Slack channel and pick which HubSpot user gets the tasks when the company is brand new.
- Set the noise filter. Tell the agent which phrases like contractor, temporary, or backfill should knock a posting out of the results.

## FAQ

### How is this different from buying a static prospect list?

A list is a one-time snapshot. This watches the job market every morning for live hiring intent, so the accounts you see are the ones taking action right now, not names from a quarter ago.

### What stops the same company from showing up twice?

Before doing anything else, the agent checks HubSpot for an existing company at the same domain. If one is already there it just refreshes the hiring-signal flag and skips the digest slot instead of creating a duplicate record.

### What if the company is not in HubSpot yet?

The agent creates a new HubSpot company using the domain and firmographics from the job posting, then attaches the task to a default rep you configure. That way net-new accounts land in your CRM the moment they show hiring intent.

### How does it decide what counts as a real buying signal?

It reads the posting and drops obvious noise like contractor gigs, temp roles, and same-title backfills. Senior leadership reqs, sales and SDR clusters, and clear team-building patterns get through. You can steer this with your own list of skip phrases.

### Which job boards does this cover?

It runs through a jobs API on the RapidAPI Hub that aggregates public postings from major boards like LinkedIn, Indeed, and Glassdoor along with company career pages. One RapidAPI subscription covers all of them.

Use this prompt in General Input: https://www.generalinput.com/prompts/daily-job-board-hiring-signals-into-hubspot-and-slack