Skip to main content
The Integration Hub connects OfficeRidge to external systems. Product ground truth lives in the app catalog (integrations-catalog.ts); this page mirrors 22 hub entries plus platform services.
The Integration Hub requires Organization Admin. It is visible on every plan, but connecting an outside system requires Professional or higher. See Plans and modules.

​
Integration tiers

Connect subject format: t:{organizationId}:u:{userId} — never org-only.

​
Live today

Faysan is the in-app operations assistant (/assistant). It answers with counts and record links only. It never receives names, dates of birth, Medicaid IDs, diagnoses, or notes. Org admins can review and revoke Connect grants at Integrations → Connections (/integrations/connections).

​
Roadmap (coming soon)

Grouped by category. None of these can be connected in production until the product marks them active.

​
Storage & files

​
Events & automation

Roadmap connectors in this category are listed below under other categories or Connect OAuth.

​
Forms & data

​
Identity & productivity

​
Email & AI

​
Billing & claims

​
Clinical & payroll

Integrations marked coming soon cannot be connected yet. Do not build a process that depends on one — in particular, EVV aggregator submission and claims clearinghouse EDI are not yet available through OfficeRidge.

​
Platform services (not org hub connectors)

These are not “connect your EVV vendor” integrations — they run the OfficeRidge platform.

​
Status labels

Each integration card shows one of:

​
Box (Connect OAuth)

Each user authorizes their own Box account via Vercel Connect (box/officeridge). Files stay in your agency’s Box tenant. OfficeRidge stores metadata and folder mappings only.
Because files remain in your Box tenant, the security of member documents stored there depends on your Box configuration — not on OfficeRidge alone. Review Box sharing settings and put a business associate agreement in place before storing PHI. See HIPAA compliance.

​
Webhooks

Webhooks send signed HTTPS callbacks to a URL you control when members, forms, files, and incidents change.
Webhook payloads may describe changes to member records. Send them only to an endpoint your agency controls, over HTTPS, with a business associate agreement if a third party operates it.

​
Connections (org admin)

At Integrations → Connections, organization admins can list active Connect OAuth grants for the org and revoke access without opening each integration page.

​
Connecting an integration

1

Confirm your plan and role

Organization Admin, on Professional or higher.
2

Assess the PHI implications

Determine whether the integration will handle member information.
3

Put a business associate agreement in place

If a third party will handle PHI, before connecting. See HIPAA compliance.
4

Configure and connect

Follow the integration’s setup prompts.
5

Verify the status shows Connected

Then test with non-sensitive data first.

​
Troubleshooting

Workflow automation

Automation credentials and run history.

HIPAA compliance

Business associate agreements.