Choose a workflow
Build and qualify prospect lists
Build an AI outbound campaign from a prompt
Describe your buyer in plain English, save an enriched list, and launch AI-written email grounded in your product.
Qualify leads with AI before you enrich them
Score a raw list against your ideal customer profile with a smart column, then enrich only the leads that pass.
Turn a Deep Research run into a campaign
Research a niche market with one prompt, keep the report as campaign knowledge, and reach the people it found.
Run outreach on buying signals
Automate job change outreach
A signal agent finds people starting a new role, and a dynamic campaign contacts each one automatically.
Reach newly funded companies
Turn funding announcements into the leaders you sell to at each company, enrolled as they arrive.
Turn website visitors into pipeline
Find the decision-makers at the companies visiting your site and reach them the same day.
Personalize, follow up and keep data clean
Personalize every email with AI research
A smart column researches every prospect and writes an opening line you can check before it is sent.
Follow up on replies and clicks
Hand repliers to your CRM and give people who clicked but never replied a second touch.
Clean and enrich your CRM data
Import a CRM export, merge duplicates, verify and enrich contacts, then sync them back.
How the Fuse tools connect
Five mechanics make the API composable. Every workflow relies on at least two of them, and knowing them makes it easy to design your own.Lists are the hand-off
Almost every tool either fills a list or works on one. Pass the list id along and the next tool picks up where the last one stopped.
Enrichment, smart columns, exports, CRM pushes and campaigns all take a list id.
One row filter everywhere
GET /business/lists/{listId}/rows, POST /business/lists/{listId}/enrich, POST /business/lists/save-to-list and smart columns accept the same filters object. It can match the values in your custom and smart columns:
yes also matches Yes.. That means an answer written by an AI column can decide which rows you enrich, copy or contact next.
Companies lead to people
A company domain is the bridge from accounts to the people who work there. Pass domains, up to 1,000 at a time, as thejob_company_website filter of a people search to find the right contacts at those companies. GET /business/lists/{listId}/filter-values?field=domain returns the domains in a company list, up to 1,000 rows per call, and the website visitor feed returns the domain of each visiting company. Funding round outreach shows the step end to end.
Columns feed the copy
A campaign step can insert any custom or smart column with a token such as{Column: Opener}, so whatever you write into a list can end up in the email. The value is read when each contact’s step is scheduled, so fill the column for everyone first: a blank cell leaves a gap, and a contact whose smart column is still running is stopped rather than held. Personalize every email with AI research shows the safe order.
Campaigns keep enrolling
A campaign created withisDynamic: true checks its source lists about every 30 minutes and enrolls contacts that are not in it yet, up to 200 at a time, however they got onto the list. Point one at a list that keeps growing, such as an agent’s results list or a list you save into every day, and outreach continues without another call. A check enrolls nobody while you have no usable sending account, or while one of the campaign’s exclude lists cannot be read; the next check tries again.
What every workflow has in common
- Async steps answer
202. Each workflow names the call to poll for every step. The full map is in Long-running work. - Most credits are spent by the background work, not by the call that starts it. Check
GET /business/creditsbefore a large step, and see Credits & billing for what each operation costs. - Each surface has its own rate limit. Campaigns and knowledge hubs share 30 requests a minute, so poll them gently.
- Each workflow lists the scopes it needs. Keys created in the API Cockpit carry every scope, so treat each key as full access and keep one per integration, so you can revoke it on its own.