Connecting Flux to Your Outreach Stack

Edge

Build a segment of engaged prospects in Flux, export as CSV, and import into Clay, Instantly, HubSpot, or whatever tool runs your outreach. Flux does not have a direct CRM integration yet, but segments and the outreach queue give you clean, structured prospect data that drops into any tool that accepts a CSV or JSONL file.

What you'll learn

Building segments to define outreach-ready audiences
Resolving a segment and exporting a fresh prospect list
Using the constellation outreach queue for prioritized prospect lists
Import patterns for Clay, Instantly, and HubSpot

What is a segment and why does it matter for outreach?

A segment is a saved audience slice -- a group of people you define by criteria or curate by hand. Flux supports two main types:

Smart segments use predicates you set, like "title contains VP" or "works at a company with 'Acme' in the name." Every time you resolve a smart segment, Flux re-evaluates the predicates against current data and returns whoever matches right now.
Manual segments are hand-curated lists. You add specific people to them using add_to_segment, and the membership stays fixed until you change it.

Smart segments keep your outreach lists fresh without manual list-building. Someone new who matches your criteria shows up automatically the next time you resolve. Manual segments give you precise control when you want to curate a specific target list.

Ask Claude to create a segment that matches your ICP:

create_segment(
  name: "VP-level at target accounts",
  type: "smart",
  config: { title_contains: "VP", company_contains: "Acme" }
)

The supported smart-segment predicates are title_contains and company_contains. You can also use list_segment_templates to see pre-built segment templates and spin one up with a single template parameter.

For engagement-based targeting, use a manual segment and populate it from your engagement graph -- pull engagers with get_post_engagers_by_company or get_post_set_engagers, then add the people who match your criteria with add_to_segment.

How do you get a fresh prospect list from a segment?

Once a segment exists, resolve_segment evaluates it against the latest data and returns the current member list as a set of person IDs.

resolve_segment(segment_id: "seg_abc123")

The output is a list of person_ids and a count. To get the full profile details (names, titles, companies, LinkedIn URLs), use the dashboard export or ask Claude to look up the people.

Run resolve_segment before every outreach push to make sure you are working from current data, not a stale export from last week. Resolving a segment is free -- it costs 0 credits.

How do you export segment data for your outreach tools?

Flux supports CSV and JSONL export from both the dashboard and MCP tools.

From the dashboard: Open the segment detail view, click Download CSV or JSONL. The file downloads immediately with all current members and their profile fields.

From MCP tools: Resolve the segment via resolve_segment, then ask Claude to format the output for your outreach tool. The MCP tools return structured data, so any MCP client can pipe the results into a file or directly into another tool.

The export includes these fields: full name, current title, current company, headline, location, LinkedIn URL, LinkedIn member ID, date added to segment, first seen date, and last updated date.

CSV is the right choice when you are importing into Clay, HubSpot, or most CRMs. JSONL works better when the data flows into a script or automation pipeline.

The CSV export includes profile fields but not engagement counts. To get engagement context alongside profile data, use get_outreach_queue with a segment_id -- it returns both person details and engagement counts ranked by warmth.

How does the outreach queue work?

The outreach queue gives you a prioritized list of people, sorted by who is warmest and most ready for contact. It works in two modes depending on how you scope it:

Campaign-scoped (full scoring): If you have set up a Constellation campaign with create_campaign and mapped target accounts with map_constellation, the queue returns entries ranked by a composite warmth score that factors in engagement patterns, connection pools (coworker, engager, mutual), and recommended next actions.

get_outreach_queue(campaign_id: "camp_abc123")

Segment-scoped (engagement count): Pass a segment ID and the queue ranks members by how many times they engaged with your tracked profiles' posts. Simpler than the full Constellation scoring, but useful when you want a quick prioritized list without setting up a campaign.

get_outreach_queue(segment_id: "seg_abc123")

Use segments and the outreach queue together: build a segment for your ICP, then pass it to get_outreach_queue to prioritize the order you reach out.

Credit costs for constellation mapping

Setting up a Constellation campaign is the most powerful outreach workflow in Flux, but it uses credits. map_constellation costs up to approximately 175 credits per target company (actual cost varies and is reported in the response). With 200 credits per month on Edge, plan your mapping runs carefully. Call get_cost_estimate before running an expensive tool to preview spend.

How do you import Flux data into Clay, Instantly, or HubSpot?

The workflow is the same across tools: export from Flux, import into your outreach platform, and map the columns.

Clay. Import the CSV as a new Clay table. Map LinkedIn URL to the profile column so Clay can enrich further. The segment data from Flux gives Clay a pre-qualified list it cannot build on its own -- these are people who actually engaged with content in your space, not cold contacts from a directory.

Instantly. Upload the CSV as a lead list in Instantly. Map name, company, and LinkedIn URL. If you used get_outreach_queue or get_engagement_brief before exporting, you have engagement context that makes strong personalization fodder for your email sequences. A message that references their comment on a specific post converts far better than a generic template.

HubSpot. Import the CSV as contacts. Map LinkedIn URL to the LinkedIn profile property, and consider creating a custom property for "Flux segment" or "date added" so your sales team can see which contacts came from engagement-based prospecting.

In every case, the key is that Flux gives you warm prospects with context, not cold leads scraped from a directory. The engagement history is the differentiator -- it turns "person at company" into "person who engaged with content about X."

What about direct integrations?

Webhook and direct CRM integrations are on the Flux roadmap. When they ship, you will be able to push segment changes directly to HubSpot, Salesforce, or an outreach tool without the CSV step. For now, the export-and-import workflow is reliable and takes under a minute per push.

FAQ

Can I automate the segment-to-outreach workflow? Not yet as a one-click automation, but MCP tools make it scriptable. You can ask Claude to resolve a segment and format the output as CSV in a single conversation, which takes about 30 seconds. Direct integrations are on the roadmap.

How often should I re-resolve a segment before exporting? Every time you run an outreach push. Flux data refreshes daily on paid plans, so resolving a segment gives you membership that reflects the latest profile data. Exporting a week-old list means you miss anyone new who matches since then.

Does Flux enrich contacts with email addresses? No. Flux provides LinkedIn profile URLs, names, companies, and titles from engagement data. For email enrichment, import the Flux CSV into Clay or Apollo, which specialize in contact-to-email resolution. The LinkedIn URL from Flux gives those tools a reliable anchor for matching.

Can I export the outreach queue the same way as a segment? The outreach queue returns structured data through MCP tools that you can ask Claude to format as CSV. The dashboard segment export has dedicated Download CSV and JSONL buttons. The outreach queue does not have a dashboard export button -- use the MCP tools for that.

What data does the segment CSV export include? Full name, current title, current company, headline, location, LinkedIn URL, LinkedIn member ID, date added to segment, first seen date, and last updated date. Engagement counts are not included in the CSV -- use get_outreach_queue(segment_id: "...") through MCP tools to get engagement-ranked data with counts.

What is the difference between a segment and the outreach queue? Segments define who qualifies -- they are saved audience slices. The outreach queue tells you who to contact first by ranking segment members (or campaign targets) by engagement warmth. Use them together: build a segment for your ICP, then pass it to get_outreach_queue to prioritize order.

On this page