Guides: N8n

Send HealthPipe exports to n8n

HealthPipe reads selected Apple Health data on your iPhone and sends it to an HTTPS receiver. n8n can receive that export, then store it or forward it to another service.

Flow: HealthPipe → n8n Webhook → your storage or API.

1. Create the receiver

Add a Webhook node with HTTP Method set to POST. Use an HTTPS address reachable from your iPhone. For self-hosting, configure your public HTTPS webhook address; localhost on your computer is not reachable as localhost from your phone.

Use Header Auth if you want to require a shared secret, and configure the matching header name and value in HealthPipe. Do not publish your webhook URL or credentials.

2. Connect HealthPipe and test

In n8n, select Listen for Test Event and copy the Test URL. In HealthPipe, enter that URL as your destination, choose JSON, select a small date range and a few metrics, and tap Sync Now. Inspect the incoming request before building the remaining steps.

HealthPipe sends the export itself in the POST body with Content-Type: application/json. Its top-level JSON field is metrics, an array of metric objects containing name, units, and data. Data fields vary by metric. Do not use the old example payload containing comments or userid; use the real sample received from your test.

3. Store or forward the export

Connect the webhook to your chosen storage node. To forward JSON to another API, add an HTTP Request node, use POST and a JSON body, and map the received body with the expression {{ $json.body }}. Add only the authorization required by that destination. If you want spreadsheet rows, transform the nested metrics and their data arrays first.

4. Use the production URL

Publish or activate the workflow, then replace HealthPipe’s temporary Test URL with the Production URL. Test Sync Now again and check the workflow execution and final destination. A test listener is not a permanent receiver.

Delivery and scheduling

Choose the recurring export cadence in HealthPipe. An n8n Schedule Trigger cannot read Apple Health from your phone or make HealthPipe export on demand; it can process data your workflow has already received.

If the webhook responds immediately, HealthPipe’s success status confirms acceptance only. Inspect later workflow steps for failures. For stronger confirmation, design a prompt response after durable storage. Long workflows can cause timeouts, and retries can create duplicates.

Rolling date ranges overlap. Deduplicate or replace matching metric/date/source records rather than adding each delivery as new data. iOS determines when background exports can run, so exact delivery times are not guaranteed.

n8n and downstream services receive your health data. Review their access controls and execution-history retention before using real exports.

Reference: n8n Webhook documentation. Reviewed October 2, 2026.