Is Zapier HIPAA Compliant for Between-Session Follow-Up?
Outline
Maya is fictional. Her practice uses a form for a between-session diary check-in and a Zap that would create a follow-up task. The trigger’s sample payload contains her email address and the free-text reply: “I left the staff meeting early again because I felt close to tears.” The filter tests whether the Zap continues. The downstream action is configured without mapping the email address or reply, so it creates a task that says only “review check-in.”
The task looks sparse because the email address and reply were not mapped to the action. The filter decides whether the Zap run continues; it does not remove fields from the trigger payload. The trigger received the email and individualized response before the filter ran, and the task history may retain a test or run copy. The data passed through the intermediate processor even though the final task contains little or nothing.
Turn down the clinical Zap. Do not test it on a real reply, and do not substitute a de-identified real note. Keep stock-reorder alerts in the admin automation, using only nonclinical inventory details. Collect Maya’s individualized response through the clinical check-in workflow.
Print the Zap trace sheet
Trace a Clinical Zap
Use the sheet this week to map the trigger, filter, history, and safer check-in owner before changing a workflow.
- Practice Wiki Template Release Check for inherited access and synthetic retrieval
- Handwritten Working Note: Keep, Transmit, or Chart? for sync, backup, AI, support, and chart entry
- Trace a Follow-Up Before Enabling a Zap for trigger data, filters, downstream actions, and history
- Outcome Tracker: Staff Record or Patient Portal? for org-unit eligibility, interface access, AI terms, and client response location
Free. We'll email the PDF link right away and add you to the therapist toolkit, sent every two weeks. Unsubscribe any time.
Where should we send the link?
We'll email the PDF link right away. You'll also get the therapist toolkit every two weeks. Unsubscribe any time.
✓ Check your inbox
We've sent you the PDF
The download link is on its way to your inbox, usually within a minute or two. The email will come from Emosapien (hello@team.emosapien.com); check your spam folder if you don't see it.
You're also on the therapist toolkit list, sent every two weeks. Unsubscribe any time from the email footer.
Record the trigger, fields received, filter condition, downstream action, and retained history so you can trace your own workflow without entering client data.
Keep PHI out of Zapier: the service does not support workflows involving PHI and does not sign a BAA for it. Zapier’s “Data Privacy Overview” and “Is Zapier HIPAA compliant?” pages were checked November 2026; recheck those terms before changing your workflow.
Start at the trigger, not the task
A form trigger begins the data path. It receives the submission so later Zap steps can evaluate it. The sample payload can therefore expose the incoming free text and contact details before a filter decides whether the run continues. A filter controls whether the Zap continues; it does not remove fields from the trigger payload.
Keep the two questions separate in your decision note: what protections the service describes, and whether it accepts this use at all. Zapier’s “Data Privacy Overview” and “Is Zapier HIPAA compliant?” pages, checked November 2026, state that PHI workflows are unsupported and that Zapier cannot sign a BAA for PHI. A safeguard cannot reverse a prohibited data path.
Do not assume a paid-plan exception. Zapier’s “Data Privacy Overview” and “Is Zapier HIPAA compliant?” pages, checked November 2026, do not describe one. A higher price, workspace control, or security feature is not permission to send PHI. Keep safeguards separate from whether the service supports this data use.
A BAA with the form provider or your EHR does not cover a separate intermediary. Each organization’s role and contract apply to its own handling; a downstream recipient’s agreement does not create an agreement with every service data passes through. HIPAA applicability depends on the practice and the workflow, so take contract questions to counsel rather than treating this as legal advice.
Follow the sample payload through each step
Write down what enters the Zap before you inspect the action output. Include the trigger type, each sample field, whether a test run captured it, the filter condition, the action fields, and any task-history or replay copy. A clean-looking action record cannot prove that the trigger never received the source data.
Do not test this path with a real client response. Even changing the name leaves potentially identifying details in timing, workplace, relationships, location, or the story itself. For HIPAA Safe Harbor, 45 CFR 164.514 requires removal of 18 identifier categories, including identifiers of relatives, employers, and household members, and no actual knowledge that remaining information could identify the person. Expert Determination is a separate method. HHS explains both routes in its de-identification guidance. Removing a name is not by itself HIPAA de-identification.
HIPAA is not the only constraint. Professional guidance from a licensing body or association is guidance, not a national statute; state rules apply within their jurisdiction and may add obligations. A client consent form does not turn a vendor-prohibited workflow into a permitted one. Ask your counsel or privacy officer to assess the specific practice and workflow. For a broader way to document safeguards and threats, use the HIPAA risk-assessment guide.
Keep the automation nonclinical
A stock alert can remain in an admin automation when it contains inventory facts only: “order printer paper” or “reorder intake folders.” Do not attach client identifiers, check-in text, diagnoses, appointment context, or a link that reveals a client’s record. Keep the trigger’s source and sample data free of clinical details, not merely the action’s final message.
A shorter task-history period can reduce how long Zap history remains available, but it does not make PHI use acceptable. Zapier’s “AI Automation Platform: Legal and Compliance Information” page, checked November 2026, says Enterprise customers can reduce task-history retention to seven days and are automatically opted out of model training on their content; other customers may opt out. Keep those controls in perspective: Zapier’s “Data Privacy Overview” and “Is Zapier HIPAA compliant?” pages, checked November 2026, state that PHI use is unsupported and Zapier cannot sign a BAA for it. A later filter, shorter history, or model-training opt-out cannot reverse receipt at the trigger.
For documentation, the clinical record remains the place for your review and signature. Do not use a general automation task list as the clinical record or as a substitute for your practice’s approved recordkeeping process.
Emosapien’s Engagement Agent supports guided check-ins, AI-assisted journaling, and modality-aligned homework in the client app on Professional and Enterprise plans. The Scribe Agent drafts progress notes for clinician review, editing, and signature. These tools give you a clinical workflow for client engagement and documentation; they do not make a separate automation workflow appropriate for PHI.
Keep a decision record
File a short decision record before the next workflow change. Keep the trigger name and source, a list of sample fields without any actual client data, the filter condition, the downstream action, and where test copies or task history may remain. Record the nonclinical workflow you retained, the clinical check-in owner, and who approved turning down the Zap. Preserve vendor terms by exact page title and date checked, not by a copied screenshot alone. For questions about what records to retain and review, see the HIPAA audit-log review and retention guide.
Use the current Zapier terms to guide your workflow decision. Zapier’s “Data Privacy Overview,” “Is Zapier HIPAA compliant?”, and “AI Automation Platform: Legal and Compliance Information” pages, checked November 2026, state that PHI use is unsupported and Zapier cannot sign a BAA for it. The “AI Automation Platform: Legal and Compliance Information” page also describes Enterprise task-history reduction and training opt-out choices. Treat those as operational safeguards, not permission to send PHI, and recheck the pages before making a new vendor decision.
As a US clinician, apply this guidance to your role and the facts of your practice with counsel or your privacy officer. HIPAA duties depend on those specifics, and state privacy, licensing, and professional requirements may also apply. A signed agreement or consent does not guarantee that a particular workflow is compliant.
Keep client details in the clinical record
Use the clinical check-in workflow for an individualized reply, and keep Zaps for genuinely nonclinical administration. Emosapien’s Engagement Agent supports guided between-session check-ins and journaling on Professional and Enterprise plans; you remain responsible for clinical decisions and documentation.
Collect the next reply in a guided client check-in
Professional and Enterprise plans include guided client check-ins. Keep individualized replies in a clinical workflow, with you reviewing the documentation.
Start free- Professional and Enterprise
Client reply
I felt close to tears after work.
Next step
Bring this check-in to session.
References
- HHS, “Guidance Regarding Methods for De-identification of Protected Health Information,” checked November 2026.
- Zapier, “Data Privacy Overview,” checked November 2026.
- Zapier, “Is Zapier HIPAA compliant?”, checked November 2026.
- Zapier, “AI Automation Platform: Legal and Compliance Information,” checked November 2026.
- 45 CFR 164.514, checked November 2026.
Related reading
Best HIPAA Compliant Email for Therapists: Mailbox or Encryption Add-On?
Compare therapy email mailboxes and encryption add-ons on BAA scope, client reply friction, attachments, administration, export, retention, and cost.
Read article →Best HIPAA Compliant Note App: Therapist Buying Guide
Compare the best HIPAA compliant note app options by BAA terms, therapy formats, note separation, access, export, and clinician review.
Read article →Free PDF: Practice App PHI Release Checks
Four printable release checks help clinicians test practice-app access and data paths with fictional information before approving a workflow.
- Practice Wiki Template Release Check for inherited access and synthetic retrieval
- Handwritten Working Note: Keep, Transmit, or Chart? for sync, backup, AI, support, and chart entry
- Trace a Follow-Up Before Enabling a Zap for trigger data, filters, downstream actions, and history
- Outcome Tracker: Staff Record or Patient Portal? for org-unit eligibility, interface access, AI terms, and client response location
Free. We'll email the PDF link right away and add you to the therapist toolkit, sent every two weeks. Unsubscribe any time.
Where should we send the link?
We'll email the PDF link right away. You'll also get the therapist toolkit every two weeks. Unsubscribe any time.
✓ Check your inbox
We've sent you the PDF
The download link is on its way to your inbox, usually within a minute or two. The email will come from Emosapien (hello@team.emosapien.com); check your spam folder if you don't see it.
You're also on the therapist toolkit list, sent every two weeks. Unsubscribe any time from the email footer.