⭐ Available in the following bundle: Core Bundle
⭐ Bundle included in the following plans: Starter, Growth, Scale, Enterprise
⭐ Available on the following legacy plans: Basic, Pro, Agency, Business
👀 Not sure which plan you're on? Check your subscription here.
Connect Heyflow with Make to integrate your funnel responses with over 3,000 tools and automate workflows using simple if-this-then-that logic. Each Make automation, called a scenario, can use a Heyflow response as a trigger to perform actions in one or more connected tools.
With Heyflow's Make integration you can:
Hand off leads seamlessly from funnel to Make
Send Heyflow submissions straight into Make - easy to set up.Capture clean, structured lead data in Make
Use all data from Heyflow submissions and map Heyflow fields directly to any connected tool.Automate complex workflows
Create multi-step automations across multiple tools to control exactly what happens after a funnel response.
💡 Tip: Popular use cases are connecting your Heyflow with your CRM or your email marketing tool to collect new contacts or enhance them with information from your flow.
❗ Note: Heyflow can only be used as a trigger, not an action.
Setup
Step 1: Create a scenario
Sign up or log in to your Make account and go to the Make dashboard. Click on 'Scenarios' and '+ Create a new scenario' top right.
Create your first module by clicking on the plus sign and choose "Webhooks", since we don’t have a native app in Make.
Select 'Custom webhook'.
If it's your first webhook, then click on 'Create a webhook'. If you've already used a webhook in the past, click on 'Add'.
Now insert a name for your webhook, and click on 'Save'.
Step 2: Integrate with Heyflow
You immediately get a webhook URL, that you can copy.
Within your flow, go to 'Connect' and then to the tab 'Response Handlers'. Go to Make under 'Automation Platforms' and insert your webhook URL in the integration and click on 'Connect'.
💡 You can use webhook URLs from any Make region, for example hook.eu1.make.com, hook.eu2.make.com or hook.us1.make.com. Make Enterprise domains (e.g. eu1.make.celonis.com) are supported as well. Always copy the full URL from your Custom webhook module.
Step 3: Set up an Action
Head back to Make and save your webhook.
Now create your second module as an action after the webhook, for example Slack. To do this, select the action to be performed, such as ‘Send a message’.
Click on ‘Add’ to connect your Slack account and enter your ‘Connection type’ and ‘Connection name’. Then save your settings by clicking ‘Save’. You may need to grant app permissions here so that the data can be transferred.
Now you can configure the individual settings. Select ‘Direct message’ if you want to receive a direct message as soon as a user completes the flow. Also select the ‘Channel type’ and then the corresponding ‘User’. Enter a message in the text field that should be sent each time a user submits your flow. You can customise this message later. However, a test run will be started first.
Save your settings by clicking ‘Save’ and then click ‘Run once’.
Now go back to your flow and start a short run-through of your flow so that a response is transmitted in the flow and can be captured by Make.
Now go back to Make. Click on the text field in your Slack module. Your Heyflow fields will now be successfully mapped in Make. You can now start structuring your message. Simply drag and drop the various blocks into the text field.
Now click on ‘Save’. The scenario is now set up and running. You have successfully connected your Heyflow to Make. Have fun automating!
Use Case: Automated Downloads
With Make you have the functionality to download files automatically.
This enables a faster processing of uploaded documents in your CRM tool, e.g., directly as a PDF file or uploading a file, e.g., in your Google Drive.
This is how it works
In order to use this function, you need to connect HTTP integrations with Make.
Select the action:
Get a file.
You can now select the URL from the triggered responses via the webhook and use the generated file in the next steps of the scenario.
❗Public file access needs to be enabled in the settings of your flow. This is an important requirement to make it work.
Troubleshooting
If something goes wrong with your integration, an automatic email notification will be sent. The message includes the flow ID, response ID and a description of the error returned by your integration.
I don’t see all responses in Make
If your flow uses Conditional Logic, make sure you test all possible paths to capture the full set of fields. The easiest way to achieve this is to navigate through all screens directly in the Heyflow app, input data for all fields, and send the test response directly from the app. This ensures that Make receives the complete data structure.
I don’t see any URL/UTM parameters in Make
Make only shows parameters that are included in the submitted response.
To be able to map URL or UTM parameters (e.g. utm_source) in Make, you must manually add them to the URL when submitting your test response. For example: your.domain.com/yourflow?utm_source=Google&utm_campaign=test
Error "Unable to activate Make integration"
Heyflow checks your webhook URL as soon as you click 'Connect'. If you see this message, check the following:
The URL comes from a Custom webhook module in Make and was copied completely (no spaces).
The webhook still exists in Make and was not deleted.
Your scenario is open and the webhook module is waiting for data ('Run once' is active) while you click 'Connect' in Heyflow.
If in doubt, create a new webhook in Make and paste the new URL.
Make does not receive any responses?
Heyflow only sends responses to Make when at least one owner of your organization has verified their email address. If no owner is verified, responses are still saved in Heyflow, but they are not sent to Make or any other integration.
In this case you see a warning in your flow under 'Connect'. Click the verify action in the warning, or open the verification email we sent to the owner, and confirm the email address. New responses are then sent to Make again.
Error "Queue is full"
This message comes from Make. The queue of your webhook is full, so Make rejects further responses and they do not reach your scenario.
Every webhook in Make has its own queue. Its size depends on your Make credits: per 10,000 licensed credits per month, a webhook can hold up to 667 waiting items, with a maximum of 10,000. Check your webhook queue in Make and make sure your scenario is active, or increase your Make credits.
🔎 For a list of common issues and general recommendations, check out the Troubleshooting Guide for Response Handlers.