Integrations

Connect sign-in, billing, email, and EI Hub file exchange without splitting the child record.

Tiny keeps the child record as the source of truth, then uses narrow data paths for account access, subscription billing, account email, 837P submissions, acknowledgments, and payment returns.

Create free agencyPlan a migration

A narrow connection is safer to understand.

Every handoff names the data, direction, person responsible, and recovery path.
  • EI Hub file workflows use the formats agencies already exchange
  • Stripe receives subscription data, not child records
  • Account email never includes child or family information
  • A connection inherits the same agency permission boundary
Current data paths

Use an online connection where one exists and a traceable file workflow where it does not.

Some systems expose an online connection. EI Hub work still relies on controlled file exchange, so Tiny Solutions treats the file, status, and return record as one traceable handoff.

File handoff

EI Hub claim submission

Build 837P files from verified claim data, then mark the file when the agency uploads it to EI Hub.
File handoff

EI Hub acknowledgment and payment returns

Ingest 277CA acknowledgments and State Fiscal Agent payment CSV files so the return path stays tied to the submitted claim.
Agency setup

Google and Microsoft sign-in

Configured sign-in providers can join passkeys, email methods, and agency security policy without creating a second account model.
Built in

Stripe

Stripe handles the Tiny Solutions subscription. Child records and EI Hub claim details do not go to Stripe.
Built in

Account email

Transactional email carries sign-in and account information only. Child and family information stays out of every message.
EI Hub

Prepare, submit, and reconcile EI Hub files from the same claim history.

Tiny Solutions does not pretend that a portal upload is a live online connection. The product keeps the submission and return evidence together so staff can see what happened next.

Prepare

Verified claims become a controlled 837P file with submission identifiers the return path can match.

Submit

The agency uploads the file through its approved EI Hub process and records that handoff in Tiny Solutions.

Reconcile

277CA acknowledgments and State Fiscal Agent payment files return to the same claim history.
Data access

Use documented exports instead of a promised API that does not exist.

Tiny Solutions does not currently publish general API credentials or promise an online connection that the product does not provide. Agency exports and the documented handoffs remain the dependable route today.

Need to move existing records?

Start with the source export and active caseload. The migration guide explains how to scope a safe transfer before real child data moves.
Read the migration guide

Need a connection reviewed?

Describe the outside system, data direction, frequency, and person responsible. Do not send real child data in the first email.
Ask about a connection
Start with the source of truth

Build the child record before adding another data handoff.

Create an agency and see the child-record model first. The right data handoff is easier to choose once the operating record is clear.

No card, paid subscription, or integration contract is required to begin.

Create free agencyAsk about integrations