Skip to content
TargetFlo — ABA therapy center operations software

Integrations

Bring your fax provider. Keep your workspace. Connect your payers.

TargetFlo integrates with the tools your ABA therapy center already runs on — fax, Google Workspace, eligibility clearinghouses, AI, and email — and normalizes inbound documents into one intake workflow.

TargetFlo integrations hub connecting fax providers, Google Workspace, insurance eligibility, and AI for ABA therapy center software

What are TargetFlo integrations?

TargetFlo integrations are the connections between ABA therapy center software and the systems around it: cloud fax providers such as RingCentral, Google Workspace for employee accounts, a Stedi-compatible clearinghouse for 270/271 eligibility, Google Gemini for OCR and compose assist, Google Cloud Storage for documents, and Resend for email. Each one feeds the 9-stage intake pipeline or the Workforce module rather than creating another inbox to check.

RingCentral
Google Workspace
Microsoft 365
Stedi Eligibility
Google Gemini OCR
MCP + Claude
Resend
Google Cloud Storage
eFax
SRFax
Concord Fax
OpenText RightFax
Documo / iFax
RingCentral
Google Workspace
Microsoft 365
Stedi Eligibility
Google Gemini OCR
MCP + Claude
Resend
Google Cloud Storage
eFax
SRFax
Concord Fax
OpenText RightFax
Documo / iFax
RingCentral
Google Workspace
Microsoft 365
Stedi Eligibility
Google Gemini OCR
MCP + Claude
Resend
Google Cloud Storage
eFax
SRFax
Concord Fax
OpenText RightFax
Documo / iFax
RingCentral
Google Workspace
Microsoft 365
Stedi Eligibility
Google Gemini OCR
MCP + Claude
Resend
Google Cloud Storage
eFax
SRFax
Concord Fax
OpenText RightFax
Documo / iFax
Documo / iFax
OpenText RightFax
Concord Fax
SRFax
eFax
Google Cloud Storage
Resend
MCP + Claude
Google Gemini OCR
Stedi Eligibility
Microsoft 365
Google Workspace
RingCentral
Documo / iFax
OpenText RightFax
Concord Fax
SRFax
eFax
Google Cloud Storage
Resend
MCP + Claude
Google Gemini OCR
Stedi Eligibility
Microsoft 365
Google Workspace
RingCentral
Documo / iFax
OpenText RightFax
Concord Fax
SRFax
eFax
Google Cloud Storage
Resend
MCP + Claude
Google Gemini OCR
Stedi Eligibility
Microsoft 365
Google Workspace
RingCentral
Documo / iFax
OpenText RightFax
Concord Fax
SRFax
eFax
Google Cloud Storage
Resend
MCP + Claude
Google Gemini OCR
Stedi Eligibility
Microsoft 365
Google Workspace
RingCentral

Live or flexible Roadmap · See all 8 integrations

Bring your fax provider

TargetFlo normalizes inbound documents into your intake workflow

Switching fax vendors is a project nobody wants. You keep the number, the contract, and the provider; TargetFlo takes the documents.

Fax providers

Live today

RingCentral live today. Five more through flexible connectivity.

Inbound faxes arrive by webhook, are OCR'd and AI-extracted, and land in a triage queue where a coordinator links them to a client or creates a referral card. No downloading PDFs from a portal.

  • RingCentral: inbound webhooks, scheduled sync, and SMS broadcast
  • eFax (j2 Global), SRFax, Concord Fax, OpenText RightFax, Documo / iFax via flexible connectivity
  • Fax numbers assigned per location for multi-site providers
  • Every page stored encrypted in Google Cloud Storage

Integration guides

Four integration families, each with its own guide

Live today

Fax providers

RingCentral is live with inbound webhooks, sync, and SMS. eFax, SRFax, Concord Fax, OpenText RightFax, and Documo/iFax connect through flexible connectivity.

  • Inbound documents land in the Fax Inbox
  • OCR + AI extraction on every page
  • One click to link a fax to a client or referral
Read the fax providers guide
Live today

Google Workspace & Microsoft 365

Provision, suspend, reactivate, and offboard employee accounts from the employee record. Google Workspace is live; Microsoft 365 / Entra ID is on the roadmap.

  • Org unit assignment by role and location
  • Email lifecycle tied to onboarding and offboarding
  • Waitlist for Microsoft-first organizations
Read the google workspace & microsoft 365 guide
Live today

Insurance eligibility

Real-time 270/271 eligibility checks through a Stedi-compatible clearinghouse connection, run inside the Insurance stage of intake.

  • Coverage, plan, copay, and deductible context
  • Payer mapping per organization
  • Retry and error handling built in
Read the insurance eligibility guide
Live today

AI, OCR & MCP

Google Gemini powers OCR on faxes, compose assist for messages, and MCQ generation for courses. An MCP server for Claude is on the roadmap for non-PHI operational questions.

  • Every AI feature has a documented data scope
  • PHI never leaves your controlled environment
  • MCP assistant scoped to aggregates only
Read the ai, ocr & mcp guide

How connections work

Connect, map, flow, audit

  1. 01

    Connect

    Authorize your fax provider, Google Workspace, and eligibility connection during onboarding. Most centers finish in the first two sessions.

  2. 02

    Map

    Assign fax numbers to locations, org units to roles, and payer identifiers to your plan list. Mapping lives in organization admin.

  3. 03

    Flow

    Inbound faxes become referral cards. New hires become Workspace accounts. Eligibility runs in the Insurance stage without leaving the pipeline.

  4. 04

    Audit

    Every integration action — a sync, a provision, an eligibility request — is logged with actor, timestamp, and outcome.

Design principles

Integrations built for a HIPAA-aware architecture

Connecting a system is easy. Connecting it without leaking PHI into an operational tool is the part TargetFlo designs for.

Event-driven, not polling-only

Where a provider offers webhooks — RingCentral today — TargetFlo receives documents the moment they arrive, then reconciles with a scheduled sync.

Normalized into intake

A fax, a web form, and a provider-portal submission all become the same thing: a referral card with an owner, a stage, and a linked client record.

Scoped credentials

Each connection uses least-privilege credentials stored per organization. Workspace admin scopes cover account lifecycle, not mailbox contents.

Multi-location aware

Fax numbers, org units, and payer maps are configured per location, so a six-site provider does not share one inbox or one directory tree.

PHI stays in the PHI schema

Integration payloads that carry client data are written to the isolated PHI schema; operational integrations never read from it.

Documents in Google Cloud Storage

Fax pages, signed consents, and uploaded records are stored encrypted in Google Cloud Storage and referenced — never duplicated — across modules.

FAQ

Integrations FAQs

Connect your fax provider and Workspace in the first onboarding session

Book a demo and bring the name of your fax vendor, your identity platform, and your top payers. We show the integrations running on your setup.