Chanty connects to Zapier, Make and n8n, but Chanty's BAA does not cover any data an automation sends out of Chanty. Zapier states that it does not sign a BAA on any plan and should not be used for PHI, so PHI must not pass through Zapier at all (zapier.com). Inside Chanty, the BAA on the Business and Enterprise plans covers everything in your team space. Outside it, each vendor's own agreement applies, or nothing does. Chanty has no EHR or EMR integration.
- Short answer: Zapier, integrations and Chanty's BAA
- Integrations Chanty lists
- What Chanty's BAA covers, integration by integration
- No EHR or EMR integration: what clinic teams do instead
- Safe automations that carry no PHI
- If your practice runs on Microsoft 365 or Google Workspace
- Setting up integrations safely: an admin checklist
- Integrations and BAA by plan
- FAQ
Short answer: Zapier, integrations and Chanty's BAA
Chanty's BAA stops at the edge of the Chanty team space. Anything Zapier, Make, n8n or another integration reads and sends elsewhere is not covered by it.
- Plans with a BAA: Chanty supports HIPAA compliance with a signed BAA on the Business and Enterprise plans. The BAA covers all data in the team space: messages, files, voice notes, tasks and Teambook.
- Free plan: The Free plan has no BAA and should not hold PHI.
- Third-party integrations: Third-party integrations and connected cloud storage are outside Chanty's BAA. Each vendor that touches PHI needs its own BAA with your practice.
- EHR and EMR: Chanty does not integrate with any EHR or EMR. Patient records stay in your EHR, and Chanty carries staff coordination.
For the full scope, signing process and plan requirements, see what Chanty's BAA covers.
Integrations Chanty lists
Chanty lists native integrations in seven categories. You can reach more tools through automation platforms.
| Category | Tools | What the integration does | Status |
|---|---|---|---|
| Cloud storage | Google Drive, Dropbox, OneDrive, Box | File sharing and previews | Available |
| Calendar | Google Calendar | Calendar notifications | Available |
| Project tools | Trello, Asana, Jira, ClickUp, Monday.com, Wrike, Basecamp | Project-management notifications | Available |
| Developer tools | GitHub, GitLab, Bitbucket | Developer notifications in conversations | Available |
| CRM and marketing | HubSpot, Mailchimp | CRM and marketing notifications | Available |
| Authentication | Duo | SSO and authentication | Available |
| Automation | Zapier, Make, n8n | Workflows connecting Chanty to other apps | Available |
| Coming soon | Stripe, Gmail, Google Forms, Salesforce | Listed as coming soon | Not available today |
- Wider catalog: More than 3,700 integrations are reachable, including through Zapier, Make and n8n.
- Requests: Customers can request any integration they need.
- Catalog size: Chanty's native integration catalog is smaller than Slack's. If your practice depends on many native integrations or a large app marketplace, weigh that before you choose.
- Plan limits: The Chanty team confirms the Business plan integration limit on request through chanty.com/pricing.
For everything else in the product, see all Chanty features for healthcare teams.
Move staff chat off personal phones
Chats, calls, announcements and assigned tasks for clinic staff in one workspace. HIPAA-compliant with a signed BAA on the Business and Enterprise plans.
The Free plan has no BAA: do not use it for protected health information.
What Chanty's BAA covers, integration by integration
If data leaves the Chanty team space, Chanty's BAA no longer covers it.
| Integration type | What data leaves Chanty | Covered by Chanty's BAA | What to check with the vendor |
|---|---|---|---|
| Chanty team space (messages, files, voice notes, tasks, Teambook) | Nothing. Data stays in Chanty. | Yes, on Business and Enterprise with a signed BAA | Sign Chanty's BAA before any PHI enters the workspace. |
| Cloud storage links and previews (Google Drive, Dropbox, OneDrive, Box) | Files and metadata held by the storage vendor | No | Whether the vendor signs a BAA, and on which plan. Google covers Drive and Calendar under its Workspace Business Associate Amendment (knowledge.workspace.google.com). Microsoft includes its BAA by default for in-scope services (learn.microsoft.com). Dropbox and Box sign a BAA only on some plans; see HIPAA-compliant file sharing. None of these BAAs covers third-party apps such as Chanty. |
| Zapier, Make, n8n | Any message or field the automation reads or sends | No | Whether the vendor signs a BAA. Zapier does not sign a BAA (zapier.com). BAA availability for Make and n8n cloud could not be confirmed from official sources, so ask each vendor directly. |
| Calendar and project-tool notifications | Event or task text passed between tools | No | Keep PHI out of event and task titles, or get that vendor's BAA. Each vendor's BAA covers only the services that vendor lists as in scope, not connected third-party apps (learn.microsoft.com). |
| Duo SSO | Authentication data | No | Duo's terms for authentication data. |
| AI agents and connected models (Enterprise only) | Thread content the agent reads and passes to the connected model | No, outside the standard BAA | A separate written agreement covering the models you connect, before agents touch PHI. |
Under Chanty's shared-responsibility model, your practice is responsible for several decisions:
- which integrations and AI agents to connect;
- what those integrations and agents may access;
- signing any vendor BAAs;
- managing user access and offboarding.
Chanty does not use conversations to train models. For controls, encryption and certifications, see security, HIPAA and BAA details.
No EHR or EMR integration: what clinic teams do instead
Chanty does not integrate with any EHR, EMR, practice management, pharmacy or patient messaging system. It is also not a clinical documentation, clinical handoff or clinical alerting tool.
Clinics that use Chanty divide the work this way:
- In the EHR: Patient records, clinical notes, orders and results stay in the EHR and your other clinical systems.
- In Chanty: Chanty carries operational coordination, with an owner and a deadline on each item. Typical examples:
- a front desk question about tomorrow's schedule gap;
- a broken printer at the second location;
- a supply shortage in exam room 3;
- an IT access request for a new hire;
- a follow-up task assigned to the clinic manager.
- Policies for staff chat: With a signed BAA on Business or Enterprise, staff can discuss operational details inside Chanty under your practice's own minimum-necessary policies.
- Policies for automations: No PHI goes through an automation unless that automation vendor has signed a BAA with your practice.
Some practices need patient texting that syncs to the EHR. That is a separate category of product.
- OhMD: OhMD states that it "integrates with 85+ EHR systems including athenahealth, eClinicalWorks, NextGen, Allscripts, ModMed, and many others" (OhMD, Patient communication, checked 2026-11-16).
- BloomText: BloomText describes an API that can "message patients and read their replies from your EMR integration" (BloomText, Integrate, checked 2026-11-16).
Treat tools like these as complementary to staff chat, not as replacements in either direction. To see where team chat sits next to the EHR, scheduling and billing, read about staff chat that works alongside your clinical systems.
Safe automations that carry no PHI
Automations that move only operational, non-patient data are the safest place to start. Four examples that fit clinic operations:
- New form submitted: Post a notice to an #operations channel that a new internal form arrived, with no form contents. Staff then open it in the source system. A native Google Forms integration is listed as coming soon. Today this runs through Zapier, Make or n8n.
- Supply order status: Post order confirmations or delivery updates from your purchasing tool into a #supplies channel. You can also turn an update into a task for the clinic manager, such as "Gloves backordered, find substitute by Friday."
- On-call calendar reminder: A Google Calendar notification reminds the team who covers admin on-call this week. Use staff names only.
- Project-tool updates: Post Trello, Asana or ClickUp task changes for facilities, IT or onboarding projects into the matching channel. For example: "Server room AC repair scheduled."
Rule of thumb: if the payload could identify a patient, don't automate it until that vendor's BAA is signed and reviewed. Patient-identifying data includes a name, a date of birth, an appointment time tied to a name, or a reason for visit.
If your practice runs on Microsoft 365 or Google Workspace
Chanty works alongside Microsoft 365 and Google Workspace, but its native connections to them are limited to the integrations listed above.
Microsoft 365
- OneDrive is supported for file sharing and previews.
- Chanty's apps page lists no native Outlook or Teams calendar integration (chanty.com).
- Practices deeply standardized on Teams-native meetings and telephony may be better served by Microsoft Teams. See how team chat tools compare on HIPAA.
Google Workspace
- Google Drive and Google Calendar are supported.
- Gmail is listed as coming soon.
How the agreements divide
- Any BAA you hold with Microsoft or Google covers the services named in that agreement. Microsoft's covers in-scope services under its Product Terms, and Google's covers the services on its HIPAA Included Functionality list and excludes third-party apps (learn.microsoft.com).
- Chanty's BAA covers the Chanty team space.
- Neither agreement extends to the other's data. A file shared from OneDrive or Google Drive is governed by the storage vendor's terms, not Chanty's.
Identity
- SSO, 2FA and one-time-code login are available on Business.
- SAML SSO, directory sync and SCIM are available on Enterprise.
- A Duo integration is available for authentication. Ask the Chanty team which identity providers SSO supports before you plan a rollout.
Details are on roles, permissions and SSO.
Setting up integrations safely: an admin checklist
Sign the BAA first. Sign Chanty's BAA on Business or Enterprise before any PHI enters the workspace.
Inventory every integration and automation. Record what data each one reads and sends, and whether that vendor has signed a BAA with you. A spreadsheet with four columns is enough: tool, data read, data sent, BAA status.
Restrict who can connect tools. Use roles and permissions on Business and Enterprise to limit who can add integrations. The setting is called "Create integrations" (Manage Team → Permissions and Roles). It is on by default for Owner and Admin and optional for Member, Guest and Multiguest (chanty.com).
Keep outside parties in guest access. External IT contractors, billing vendors and consultants should be guests limited to selected conversations. See guest access for contractors.
Set retention on automated channels. Business and Enterprise offer two levels of retention:
- workspace-wide retention, for example 30, 90 or 365 days, or unlimited;
- conversation-level retention, from 1 minute up to 90 days, or unlimited.
Retention applies to messages, files, voice notes, tasks and Teambook.
Get a separate agreement before AI agents touch PHI. AI agents are Enterprise only and need a separate written agreement covering the connected models. Their actions appear in a real-time audit trail, and admins can see and revoke agents.
Review at offboarding. When staff or contractors leave, remove their access and check the automations they created.
Integrations and BAA by plan
A BAA is available on Business and Enterprise, not on Free. On either plan, the BAA covers the Chanty team space only, not connected integrations.
| Plan | BAA | Integrations | Identity | AI agents |
|---|---|---|---|---|
| Free | No BAA; do not store PHI | Up to 10 (chanty.com) | Not listed for Free; SSO and 2FA start on Business | Not included |
| Business | Signed BAA covering messages, files, voice notes, tasks and Teambook | The Chanty team confirms the limit on request (chanty.com/pricing) | One-time-code login, 2FA, SSO, IP allowlisting | Not included |
| Enterprise | Signed BAA plus negotiated MSA | Unlimited integrations; Enterprise API (chanty.com); any integration can be requested | SAML SSO, directory sync, SCIM, IP allowlisting | Included; a separate written agreement is required for PHI; real-time audit trail |
- Enterprise extras: Data residency in the US, EU or APAC and an on-premise option.
- Small practices: Can start on Business to get the BAA.
- Multi-location groups: Groups that need SCIM, SAML SSO, data residency or AI agents should look at Enterprise.
- Pricing: See Chanty pricing per user for current per-user prices.
When you're ready, start at chanty.com/signup.
Move staff chat off personal phones
Chats, calls, announcements and assigned tasks for clinic staff in one workspace. HIPAA-compliant with a signed BAA on the Business and Enterprise plans.
The Free plan has no BAA: do not use it for protected health information.
FAQ
Is Chanty a HIPAA-compliant team messenger that works with Zapier?
Chanty supports HIPAA compliance with a signed BAA on the Business and Enterprise plans, and it connects to Zapier. The BAA covers data inside the Chanty team space, not data that Zapier moves to other apps.
Does Chanty's BAA cover data sent through Zapier, Make or n8n?
No. Any message or field an automation reads from Chanty and sends elsewhere is outside Chanty's BAA. That data is your practice's responsibility, under whatever agreement you hold with the automation vendor.
Does Zapier sign a BAA?
No. Zapier states that it is not HIPAA compliant, does not sign a BAA on any plan, and should not be used for PHI (zapier.com). Keep PHI out of every Zap.
Does Chanty integrate with our EHR or EMR?
No. Chanty has no EHR, EMR, practice management, pharmacy or patient messaging integration. Patient records stay in your EHR, and Chanty carries staff coordination such as tasks, questions and announcements.
Are files linked from Google Drive, Dropbox, OneDrive or Box covered by Chanty's BAA?
No. Files held by a cloud storage vendor fall under that vendor's terms. Each storage vendor's BAA covers only that vendor's own in-scope services, and Google's excludes third-party apps (workspace.google.com). Files uploaded directly into Chanty on Business or Enterprise are covered by Chanty's BAA.
Which Chanty plans include a BAA?
Business and Enterprise include a signed BAA covering all data in the team space. Enterprise adds a negotiated MSA. The Free plan has no BAA.
Can we use Chanty if we already use Microsoft 365?
Yes. OneDrive is supported for file sharing and previews. Chanty's apps page lists no native Outlook or Teams integration (chanty.com). Practices deeply standardized on Teams-native meetings and telephony may prefer Teams.
Can we request an integration Chanty doesn't list?
Yes, customers can request any integration they need. You can also connect more than 3,700 tools through Zapier, Make and n8n, keeping PHI out unless that vendor has signed a BAA with you.
Are AI agents covered by the standard BAA?
No. AI agents are available on Enterprise only and sit outside the standard BAA. Using them on PHI requires a separate written agreement covering the models you connect.
Is there a limit on integrations on the Business plan?
The Chanty team confirms the Business plan integration limit on request through chanty.com/pricing, so ask before you plan a large set of automations.