Heyflow Integration

Use this page to send Heyflow flow submissions into Ours Privacy as events. Heyflow posts each submission to a webhook URL you copy out of Ours Privacy, so no code is required on your side.

Before you start

• A Heyflow plan that includes webhooks (Heyflow calls them Hooks, available on Pro and above).
• The Ours Privacy Web SDK installed on the page that links to your flow, if you want to connect submissions to a known visitor.
• Permission to edit the Heyflow flow you want to track.

Setup

1. Create the source in Ours Privacy

1. Open Sources in the Ours Privacy app.
2. Click Add New Source.
3. Select Heyflow.
4. Copy the webhook URL shown on the source's Settings tab.

2. Add the hook in Heyflow

1. Open your flow in the Heyflow editor.
2. Go to the Connect tab and select Hooks.
3. Add a new hook, give it a name, and paste the Ours Privacy webhook URL.
4. Click Test to send a sample submission, then Activate the hook.

Note: Heyflow fires the hook when the respondent clicks the submit button. Anything entered after that submission is not sent.

3. Submit a test response and map fields

1. Complete your flow once so a real submission reaches Ours Privacy.
2. Return to your Heyflow source in Ours Privacy and open the Mappings tab.
3. Ours Privacy pre-populates the variables it saw in the submission, using your Heyflow block labels. Map the ones you care about to Ours Privacy attributes.
4. Map at least an email address or the Ours Privacy visitor ID so submissions can be associated with a person.

Connect submissions to a known visitor

Heyflow does not send tracking parameters or the visitor's identity automatically. To carry them through, add a hidden input field in your flow for each value you want, then pass it in the flow URL.

1. In the Heyflow editor, add a hidden Input field block for each value (for example ours_user_id, utm_source, utm_campaign). Set the block's variable name and system label to match the parameter name exactly.
2. Link to the flow with those values appended as URL parameters:

<a href="https://yourbrand.heyflow.site/my-flow?ours_user_id=YOUR_VISITOR_ID&utm_source=google">
  Get started
</a>

3. Map the hidden fields in Ours Privacy the same way you map any other field.

Hidden fields arrive alongside the respondent's answers, so they appear in the mapping UI after your first test submission.

Secure the webhook

Heyflow does not sign its webhook requests. On Heyflow's Business plan you can add Custom HTTP Headers or Basic Authentication to the hook if your security review requires the request to carry a shared secret. Contact support@oursprivacy.com to confirm what your account expects.

Next steps

• Map source fields to events to shape the event your flow submissions produce.
• Track and debug events to confirm submissions are arriving.
• Review the Sources overview for other form and CRM integrations.

Need help?

Contact support@oursprivacy.com if flow submissions are not showing up in Ours Privacy.