Guides: File

Save HealthPipe exports to Google Drive or Dropbox

HealthPipe sends JSON or CSV in an HTTPS POST request. It does not directly sync to a cloud-drive folder, generate a hosted download link, or provide a server API that can pull health data from your iPhone.

For recurring file storage, use a receiver that accepts the export and uploads a file to your drive. One practical setup is HealthPipe → n8n Webhook → file creation → Google Drive or Dropbox.

1. Set up a webhook receiver

Follow the Guides: N8n note to create a POST webhook, test it, and configure its production HTTPS URL in HealthPipe. Start with JSON so you can inspect the received body. Add matching authorization headers if your webhook requires authentication.

2. Create a file from the received body

In n8n, serialize the webhook’s body field into a text field containing JSON. Use Convert to File → Convert to Text File to make a binary file, choosing a .json filename. Upload the generated binary field using your drive’s upload node.

This preserves the HealthPipe export body. Converting the entire webhook item instead would also include the request headers and other metadata, which may contain credentials.

If you need CSV, either receive HealthPipe’s CSV format and preserve the raw request body as a .csv file, or flatten a received JSON export into rows before converting those rows to CSV. Inspect your webhook’s raw-body output and map the actual text or binary field; do not assume it is already an uploaded file.

3. Upload and verify

Connect your own Google Drive or Dropbox account in the automation service. Choose a private destination folder and a filename such as healthpipe-2026-10-02T120000Z.json. Run Sync Now, inspect the automation execution, and open the uploaded file to confirm its contents.

Publish or activate your workflow, use its production webhook URL in HealthPipe, and enable automatic exports in the app. A drive folder’s browser URL is not a HealthPipe receiver endpoint.

Storage and privacy

Timestamped exports are overlapping snapshots when you use rolling date ranges. Keep them as separate snapshots, or define a replacement/deduplication policy if you merge them later. Consider a naming or retry strategy that avoids duplicate files.

A successful webhook response does not necessarily mean the drive upload finished. Check the downstream upload step. iOS controls background delivery timing, so exports may arrive later than the preferred cadence.

Your automation service and cloud-storage provider will receive health data. Keep folders private, avoid retaining authorization headers in files, and review workflow execution logs and retention settings.

References: n8n Convert to File and n8n Webhook. Reviewed October 2, 2026.