Before you start
Step by step
1
Check which providers the run can use
A run chooses its own providers, so there is nothing to pick per run. A provider with
GET /business/research/providers shows which ones your runs can reach:source: "none" needs your own key before runs can use it. Adding keys for the ones that cover your market gives the run more sources to draw on.2
Start the run
Describe who you want, what makes them a fit, and the fields you need back. Send an Prompts can run to 2,000 characters.
X-Idempotency-Key header so a retry returns the same run instead of starting and paying for a second one:effort caps what the run spends on Fuse’s provider keys: low (1,000), medium (2,000, the default) or high (5,000). Steps on your own keys are billed on top. Asking for named people and their LinkedIn profiles makes the results list directly usable.3
Follow the run as it works
A run usually takes 5 to 20 minutes, and it never pauses for approval: it moves from Stop when
queued to running and then finishes. Its events show what it is doing. Pass the last seq you saw as sinceSeq to get only new events:status is completed, failed or cancelled. If the events show the run heading the wrong way, cancel it early with POST /business/research/runs/{runId}/cancel: provider steps already completed stay billed, and the rest of the reservation is released.4
Read the report and the results list
reportMarkdown is the written report. resultListId is the list of people or companies the run surfaced, and it is null when the research produced a report only. Read the list with GET /business/lists/{listId} and check its entityType.5
Turn the report into campaign knowledge
Add the report to your knowledge hub as a page, so AI campaigns can draw on what the research found:The page is indexed before the call answers, and later rebuilds of the hub never overwrite it. Content can run to 60,000 characters, and the hub must have finished building. Its owner can add pages, and so can anyone on your team when it is the team’s shared hub.
6
Turn the results into reachable contacts
What you do next depends on the kind of list:
- A contact list: find work emails with
POST /business/lists/{listId}/enrich,mode: "email"and alimit, then pollGET /business/jobs/{jobId}with thejobIdfrom the202untilstatusiscompleted. See Working with lists. - A company list: read its domains with
GET /business/lists/{listId}/filter-values?field=domain, then find the people you sell to with a people search onjob_company_website, saved withenrich: "email". Funding round outreach shows that step in full.
7
Launch a campaign grounded in the research
Create an AI campaign on the contact list. Leave Then wait for initialization, preview and approve as in steps 7 to 9 of Build an AI outbound campaign from a prompt.
knowledgeHubId out and the campaign is grounded on your team’s hub, which now holds the report. Pass it only for a hub you own: any other id answers 404 KNOWLEDGE_HUB_NOT_FOUND.What it costs
Troubleshooting
Run the whole workflow
Python script: research run to grounded campaign
Python script: research run to grounded campaign
Do it from Claude
With the Fuse MCP server connected:Run a Deep Research on independent dental groups in Texas with five or more clinics that opened a new location in 2026, including each group’s CEO or COO. When it finishes, summarize the report, find work emails for the people it found, and draft an AI campaign on that list. Don’t launch it.The assistant starts the run with
deep_research_start, checks on it with deep_research_status, then uses the enrichment and campaign tools. The report and the results list also appear in the Fuse app.
Related
Data providers
The providers Deep Research can call, and how to add your own keys.
Long-running work
Following research events and every other background job.
Knowledge hubs
Pages, notes and how hubs ground AI campaigns.
Funding round outreach
Going from a company list to the people who work there.