# Doc: https://www.hipaatizer.com/docs/integrations/zapier

> LLM view for https://www.hipaatizer.com/docs/integrations/zapier

This file contains all documentation content in a single document following the llmstxt.org standard.

## Zapier


<meta name="robots" content="index"></meta>

You can use HIPAAtizer's Zapier integration to connect your forms to non-HIPAA-compliant systems. This is especially useful when automating workflows that do **not** involve Protected Health Information (PHI), such as CRM updates, email marketing tools, or analytics platforms.

:::::warning[IMPORTANT]
Zapier is **not HIPAA-compliant**. Do **not** send PHI to Zapier. By default, HIPAAtizer excludes form fields from Zapier to prevent accidental transmission of PHI.
:::::

## Enabling Zapier Integration in HIPAAtizer

Before using Zapier, you must enable it and create an API key:

### Step 1: Enable Zapier Access

Go to: [Integrations → Integrated Accounts → Zapier](https://app.hipaatizer.com/integrations/integrated-accounts?type=Zapier)

Toggle Zapier access to `Enabled`.

### Step 2: Generate API Key

Go to: [Integrations → REST API → Create API Key](https://app.hipaatizer.com/integrations/rest-api/api-keys)

Create a new API key and use it to connect your HIPAAtizer account in Zapier.

## Trigger: New Form Submission

The **New Form Submission** trigger in our Zapier app listens for new submissions on a selected form. When a submission is received, the trigger activates and passes metadata to your Zapier workflow.

By default, this trigger includes only non-sensitive technical information, such as:

- Form Name
- Submission ID
- Form Submission Limit
- Location Information
- Anonymized Contact Information (if "Associate with Contact" is enabled in Form Settings)
- Current Workflow URL
- Links to access/download submission in PDF, CSV, JSON, etc.
- Submission Timestamp

### Optional: Include Form Fields

If your use case **does not involve PHI**, or if you're **not subject to HIPAA**, you can enable the inclusion of form field data in your Zap.

To do this, go to the **Configure Trigger** step in Zapier and set:

**"Include form fields in dropdown (PHI risk)?" → `True`**

:::::warning[ WARNING: PHI RISK]
Enabling this option may expose PHI in Zapier. Only use it if:
- Your form does not contain PHI, **or**
- You are not a HIPAA-regulated Covered Entity or Business Associate.

HIPAAtizer is not responsible for any PHI disclosures that occur through third-party integrations like Zapier.
:::::

## Action: Delete Submission

The **Delete Submission** action allows you to delete a form submission from your HIPAAtizer account by providing its `submission_id`.

This is useful for automated cleanup or compliance workflows.

### Where to Get Submission ID

The `submission_id` can be:
- Retrieved from earlier steps in the Zap (e.g., the **New Form Submission** trigger),
- Pulled from an external system already integrated with HIPAAtizer, or
- Found in the **PHI Access Log** in your HIPAAtizer dashboard.

You can also configure your form to include the Submission ID in:
- Email notifications,
- Webhooks,
- Printable PDFs.

---

If you need help configuring your integration or selecting safe data to share, contact our support team at **support@hipaatizer.com**.