Guides: Zapier

Send HealthPipe exports to Zapier

Use a Zapier webhook to receive selected Apple Health data from your iPhone, then route it to a destination you choose. HealthPipe sends the export; Zapier processes it after receipt.

1. Choose a webhook trigger

Create a Zap with Webhooks by Zapier as the trigger. Choose Catch Hook for parsed JSON fields, or Catch Raw Hook if you need the original request body for forwarding or file creation. Webhooks requires a supported paid Zapier plan; check current availability before setting up.

Copy the HTTPS webhook URL from the trigger. Treat that URL as private. Catch Raw Hook also exposes request headers, so do not copy headers into your saved export.

2. Connect HealthPipe

Enter the copied URL as HealthPipe’s destination. Choose JSON, a small date range, and a few metrics for the first test. HealthPipe sets Content-Type: application/json automatically. Add custom headers only if your receiver explicitly requires them; adding an arbitrary Authorization header does not make a standard Zapier catch URL authenticated.

Tap Sync Now, return to Zapier, and test the trigger. HealthPipe’s JSON body contains a top-level metrics array. Each metric has name, units, and a data array. Map fields from this received sample instead of using the previous comments/userid example. Leave the child-key filter blank if you want the whole export.

3. Add your destination action

For Google Sheets, transform the nested metric/data arrays into rows and map metric name, units, date, qty, and optional source. Do not expect a nested export to become spreadsheet rows automatically.

To forward the complete JSON export to your API, use Catch Raw Hook and a Webhooks Custom Request action with POST. Map the original raw body directly, set Content-Type: application/json, and add the downstream API’s credentials. Do not wrap the raw body in quotes or serialize it again. Inspect the outgoing request during testing.

4. Publish and verify

Test the destination action, publish or turn on the Zap, then run Sync Now again. Check Zap history and the final destination. HealthPipe’s successful delivery means the webhook accepted the request; it does not guarantee every later Zap action succeeded.

Important limits

Set your preferred export cadence in HealthPipe. A scheduled Zap cannot pull Apple Health records from your phone. Background delivery timing is controlled by iOS.

Rolling date ranges overlap, and retry attempts may repeat exports. Use upserts or deduplication when combining records. Zapier’s current webhook limits are 10 MB for Catch Hook and 2 MB for Catch Raw Hook. Reduce the export range or selected metrics if a payload is too large.

Zapier and your destination receive health data and may retain workflow history. Review their privacy, access, and retention settings. Keep webhook URLs, headers, and health exports out of public screenshots.

Reference: Zapier webhook trigger documentation. Reviewed October 2, 2026.