# Clinical Trial Signals — New Trials as Leads with Contacts (`opensignals/clinical-trial-signals`) Actor

New clinical trials are multi-year spending events. Official ClinicalTrials.gov API (no key): fresh recruiting trials with sponsor, phase, enrollment, sites — and the published contact names, phones & emails. Industry-sponsor filter, hiring cross-check, 0-100 score, watch mode.

- **URL**: https://apify.com/opensignals/clinical-trial-signals.md
- **Developed by:** [Andrey](https://apify.com/opensignals) (community)
- **Categories:** Lead generation, Automation, News
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Clinical Trial Signals — New Trials as B2B Leads with Contacts

*Clinical trials scraper & pharma lead finder — ClinicalTrials.gov new recruiting studies with sponsors, phases and published contact emails and phones.*

**A new clinical trial is a multi-year spending event.** The sponsor is committing to CROs, labs, sites, patient-recruitment vendors, imaging, logistics and equipment — for years. This Actor reads the **official ClinicalTrials.gov v2 API** (no key, no scraping) and turns freshly posted trials into scored lead records — including the **contact names, phones and emails** published in each study.

### What makes these leads different

- **`contacts` / `site_contacts`** 🔥 — central and per-site contact persons with **phone and email**, straight from the official registry. From record to outreach in one step.
- **`sponsor_class: INDUSTRY`** — one flag separates company-sponsored trials (commercial budgets) from academic ones.
- **`trial_score` 0–100** — freshness + phase (Phase 3 = biggest budgets) + industry sponsor + enrollment + multi-site + reachable contacts.
- **`hiring_check` + `composite_intent_score`** 🔥 — probes 7 ATS job boards: a sponsor starting a trial AND hiring is scaling operations right now.
- **`alert_text`** — ready-to-send Slack/Telegram line per trial.
- Full protocol context: phases, conditions, interventions, planned enrollment, site count, countries, official trial URL.

### Who buys this data

- **CROs & site networks:** new sponsors entering the clinic need partners — reach them the week the trial posts
- **Patient recruitment & diversity vendors:** recruiting trials with big enrollment targets are your exact ICP
- **Lab services, imaging, eCOA/EDC software:** Phase 2/3 industry trials = active vendor selection
- **Medical device & supplies:** filter by intervention/condition
- **BD & competitive intel in pharma:** watch competitors' pipeline velocity by sponsor

### Typical setups

- Weekly: `daysBack: 7`, `industrySponsorsOnly: true`, `phaseFilter: ["PHASE2","PHASE3"]`, `outputMode: flat_leads` → CSV of commercial sponsors with contacts.
- Daily alert feed: `onlyNewTrials: true` on a schedule → only trials you haven't seen, pipe `alert_text` to Slack.
- Condition-specific: `conditionFilter: ["oncology"]` + `countryFilter: ["United States"]`.

### FAQ

**Is this legal?** Yes — ClinicalTrials.gov is a public U.S. government registry; sponsors publish contact details specifically to be reached. Use contact data responsibly and follow applicable outreach laws.

**Why do some trials have no contacts?** Not all records publish them — use `requireContacts: true` to keep only reachable ones.

**Something broken?** Open an issue on the Actor's Issues tab — I respond within 1–2 business days.

***

*Part of the opensignals intent suite: [ATS Hiring Signals](https://apify.com/opensignals/ats-hiring-signals) · [Startup Funding Signals](https://apify.com/opensignals/startup-funding-signals) · [Government Contract Signals](https://apify.com/opensignals/gov-contract-signals).*

# Actor input Schema

## `daysBack` (type: `integer`):

Trials first posted within the last N days (max 180).

## `statuses` (type: `array`):

Which statuses to include. Recruiting trials are actively spending on sites and patients.

## `conditionFilter` (type: `array`):

Disease/condition search terms, e.g. `oncology`, `diabetes`, `alzheimer`.

## `interventionFilter` (type: `array`):

Intervention search terms, e.g. `antibody`, `device`, `gene therapy`.

## `sponsorQuery` (type: `string`):

Filter by sponsor name, e.g. `Pfizer`.

## `industrySponsorsOnly` (type: `boolean`):

Keep only company-sponsored trials (commercial budgets) — drop academic/government sponsors.

## `phaseFilter` (type: `array`):

e.g. PHASE2, PHASE3. Empty = all phases.

## `countryFilter` (type: `array`):

Only trials with sites in these countries, e.g. `United States`, `Germany`.

## `minEnrollment` (type: `integer`):

Skip small studies below this patient count.

## `requireContacts` (type: `boolean`):

Keep only trials that publish contact names/phones/emails.

## `onlyNewTrials` (type: `boolean`):

Remember seen trials, output only NEW ones. Schedule daily for an alert feed.

## `checkHiring` (type: `boolean`):

Probe 7 ATS job boards for industry sponsors: new trial AND hiring = hottest lead.

## `checkHiringTop` (type: `integer`):

How many top industry sponsors to probe.

## `maxTrials` (type: `integer`):

Cap on trials fetched.

## `outputMode` (type: `string`):

`signals` = full records with contact lists. `flat_leads` = one flat row per trial for CSV/Sheets/CRM.

## Actor input object example

```json
{
  "daysBack": 14,
  "statuses": [
    "RECRUITING",
    "NOT_YET_RECRUITING"
  ],
  "conditionFilter": [],
  "interventionFilter": [],
  "sponsorQuery": "",
  "industrySponsorsOnly": false,
  "phaseFilter": [],
  "countryFilter": [],
  "minEnrollment": 0,
  "requireContacts": false,
  "onlyNewTrials": false,
  "checkHiring": true,
  "checkHiringTop": 40,
  "maxTrials": 300,
  "outputMode": "signals"
}
```

# Actor output Schema

## `trials` (type: `string`):

New trials sorted by composite intent score, with sponsor and contacts

## `allResults` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("opensignals/clinical-trial-signals").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("opensignals/clinical-trial-signals").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call opensignals/clinical-trial-signals --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,opensignals/clinical-trial-signals"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/KO3S5B0Ga4fZLvXtA/builds/gU9vNS7nuG2Y1meNg/openapi.json