Skip to content
OutboundFixStart free

Integrations

It does not replace your stack. It decides what moves through it.

Data and enrichment systems find and enrich accounts. OutboundFix decides which accounts deserve sales capacity. CRM, SDR and GTM systems execute. It does not own a CRM, a workflow builder or a sales engagement platform.

Where the decision sits

After evidence, before action

Data and signal layer
  • CRM
  • Enrichment providers
  • Intent and signal tools
  • Public web
  • Internal data
Describes accounts
OutboundFix core
  • Evidence
  • Counter-evidence
  • Uncertainty
  • Policy
  • Decision argument
  • PASS
  • RESEARCH_MORE
  • KILL
Decides what deserves sales capacity
Action layer
  • CRM
  • SDR team
  • Agency
  • GTM workflow
  • Human operator
  • Other agents
Acts on accounts
The layers show where the decision sits, not a list of live connections. Today OutboundFix gathers its own evidence from each account’s official website and returns decisions in your workspace. Integrations with HubSpot and Clay are built and not yet active. No other data provider is connected.

Connected today

What flows in and out right now

Evidence in

OutboundFix reads each account’s own official website. No data provider, enrichment tool or CRM feeds evidence into a decision today.

Decisions out

Verdicts and Decision Records are read in the web workspace. Your team carries the decision into the CRM, the sequence or the research queue.

The boundary

Integrations bring evidence, not verdicts

An integration or a provider can add evidence and context to a decision. It cannot supply the verdict, override your policy or widen what OutboundFix may do. Whatever an integration sends goes into OutboundFix’s evidence graph with its source, and OutboundFix Core decides under your policy. Both integrations below are built on that boundary.

Built · not yet active

HubSpot decision loop

A company created or changed in HubSpot triggers a decision. The decision waits for a named reviewer. Once approved, OutboundFix writes four properties to the company record, so the verdict and the record behind it are visible where your team already works:

  • outboundfix_decision
  • outboundfix_decision_record_id
  • outboundfix_policy_version
  • outboundfix_reason_codes

The loop is built and tested end to end. It is not active for any customer yet, and autonomous write-back is not enabled. OutboundFix never overwrites a field it does not own.

Built · not yet active

Clay account intake

Clay finds and enriches accounts; OutboundFix decides which of them deserve sales capacity. A Clay table can send one enriched account at a time to OutboundFix for a decision. What Clay sends is recorded as context, with its provenance, and never counts as proof on its own: Clay data alone never produces a PASS or a KILL. Anything beyond RESEARCH_MORE comes from OutboundFix Core’s own research of the account’s official website.

That research runs on your workspace’s own model provider credential and is billed to you by the provider, or it does not run: OutboundFix does not fall back to a key of its own. A Clay connection holds no authority, so it cannot approve, write back or act on a decision. The intake is built and tested. It is not active for any customer yet.

  • Web workspace

    Available now

    Submit company domains, get a verdict with its evidence for each one whose research completes, define your targeting policy and re-evaluate accounts held at RESEARCH_MORE. Free for your first 10 accounts.

  • HubSpot decision loop

    Built · not yet active

    A company event triggers a decision; after human approval, four OutboundFix fields are written back to the company record. Built and tested end to end. Not active for any customer yet.

  • Clay account intake

    Built · not yet active

    A Clay table sends enriched accounts to OutboundFix for a decision. Clay data is kept as context and never decides on its own: the verdict comes from OutboundFix Core. Built and tested. Not active for any customer yet.

Everything else

Other systems and AI agents

No other enrichment provider or CRM integration is built: HubSpot and Clay above are the two, and neither is active yet. The API, the MCP server and the CLI are implemented on the governed Core V2 decision boundary. Public production access is not yet enabled. The exact status of each surface is on the developers page.

If your evidence or your next action lives in a system we do not reach, tell us which one.

Start freeDiscuss integrations →