Resources · Make integration

BlockSurvey Make integrationAutomate BlockSurvey with Make.

Every answer your survey collects can travel on to the tools your team already opens. The BlockSurvey Make integration gives you 1 trigger that picks up new responses. This page is for people new to Make: you connect your account, then build a first working flow step by step.

Try the BlockSurvey integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the BlockSurvey Make integration do for you?

The BlockSurvey Make integration links your survey account to Make, a tool where you build a scenario (an automation made of bricks called modules) without writing code. BlockSurvey brings one brick: a trigger that notices fresh responses and hands each one to whatever you place after it.

Feedback that reaches the right person. A product team can place Watch New Responses first and add a messaging or email module from another app behind it, so a comment lands where people actually read it instead of waiting inside the survey dashboard.

A running log of answers. An operations lead who likes spreadsheets can chain the trigger to a sheet or database app. Each response becomes a bundle (one item passed from module to module) and gets its own row, ready to sort or share.

Follow-up that starts without you. A recruiter or an event organizer can send each new response into a CRM or a task tool, so the next step is created the moment Make picks up the answer.

What Make cannot do here: BlockSurvey offers no action module and no universal API module in Make, so the scenario reads responses but never edits or creates anything in BlockSurvey. Make's own documentation for this app is marked as limited, which is why testing matters more than usual. If you want to see how the platform compares, the n8n vs Make page lays out the criteria, and the Make training walks through the editor if this is your first project. Stuck on a run that fails? Read Make troubleshooting.

Connect

How do you connect BlockSurvey to Make?

  1. 01

    Add the trigger and open the connection window

    In your scenario, add the Watch New Responses module, then click Create a connection. A connection is your BlockSurvey account linked to Make once; every future BlockSurvey module reuses it, so you only do this part a single time.

  2. 02

    Give the connection a clear name

    This field is optional, yet worth filling. A label such as the workspace or the team that owns the surveys helps a lot later, when several people share the same Make organization and have to pick the right account from a list.

  3. 03

    Authorize Make, then save

    Depending on what the window shows, either approve access on the BlockSurvey page that opens or paste the key BlockSurvey provides. Click Save. The module now shows your account and you can fill in its settings.

First scenario

Your first scenario with BlockSurvey

GoalWhen someone submits a response in BlockSurvey, Make passes it on to another app of your choice.

  1. 01

    Start a blank scenario

    Open the Scenarios page, create a new scenario and click the large + in the middle of the canvas. That empty circle is where your first module, the one that starts everything, will sit.

  2. 02

    Pick the BlockSurvey trigger

    Type BlockSurvey in the search box, choose Watch New Responses and link your account with Create a connection. Then fill in the module; once connected, Make lists what it can read from your account.

  3. 03

    Add the app that receives the answers

    Click the + to the right of the trigger and pick a module from another app, for instance a sheet or a chat tool. Map the values from the BlockSurvey response into its fields by clicking them in the panel.

  4. 04

    Test with a single run

    Submit a test answer to your survey, then click Run once. Each module shows a small bubble; open it to read the bundles it received and confirm the data went where you expected.

  5. 05

    Set the schedule and switch it on

    Click the clock on the first module to choose how often Make checks for responses; a new scenario starts at every 15 minutes. Turn the scenario on; every response a module processes counts as an operation on your plan.

Triggers

What starts a BlockSurvey scenario

1 module starts a scenario when something happens in BlockSurvey. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by BlockSurvey as soon as it happens.

BlockSurvey1Watch New Responses

Watch New Responses

triggerIn the docs only

This trigger gives you each fresh survey answer as its own bundle, so everything after it in the scenario works on one response at a time. It is the only BlockSurvey module in Make, so every flow on this app starts here.

How it fires
scheduled. Make checks the app on the scenario's schedule, not the moment someone submits, so answers arrive in batches at each check.
When to use it
whenever a completed form should kick off work elsewhere, like alerting a colleague.
Watch out
Make's documentation for this module is limited, so run it once on a test answer and inspect the output before mapping anything. The scheduled type is inferred from the module's name, so check for the clock badge when you add it.
Need help

Need help automating BlockSurvey with Make?

A person reads every message.

FAQ

Questions about the BlockSurvey Make integration

01Is the BlockSurvey Make integration free?
Yes, BlockSurvey is a standard app in Make, so it works on the Free plan. That plan has limits you will notice quickly: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and count usage in credits each month. Your BlockSurvey subscription is a separate matter this page does not cover.
02What do you need to connect BlockSurvey to Make?
A BlockSurvey account and a Make account. Make's documentation lists no special prerequisite for this app. In the Watch New Responses module you click Create a connection, optionally name it, then either approve access on the BlockSurvey page that opens or paste the key BlockSurvey gives you, and click Save. The connection is stored once and reused by any later BlockSurvey module. If something is unclear, remember that Make marks its documentation for this app as limited, so a test run tells you more than the reference page.
03Does the BlockSurvey trigger react instantly?
No. Watch New Responses is listed as a scheduled trigger (the type is inferred from its name, and the module shows a clock badge if so): Make asks BlockSurvey for new answers each time the scenario runs, rather than being called the second a form is sent. A new scenario checks every 15 minutes by default. On the Free plan 15 minutes is also the shortest gap allowed, while paid plans go down to 1 minute. Every response submitted between two checks is picked up together on the next one, each as its own bundle, so nothing is skipped because of the wait.
04What if the BlockSurvey module you need is missing in Make?
It depends on what you need. Make offers only Watch New Responses for BlockSurvey, and this app has no Make an API Call module, so you cannot send custom requests to BlockSurvey from a scenario. Anything that creates or changes data inside BlockSurvey is therefore out of reach here. You can still do a lot after the trigger by adding modules from other apps. For a flow that truly needs more, the Hackceleration team can look at your case and suggest another route.
05Should you use Make or n8n for BlockSurvey?
It depends on your criteria, and this page only covers Make. In Make, BlockSurvey brings one scheduled trigger, Watch New Responses, available from the Free plan, with no action and no universal API module. Whether n8n has a BlockSurvey node, and what it offers, is something to check on the n8n side before deciding. Compare the two on what your flow needs: the trigger type, the actions you want in BlockSurvey itself, and the tools your team already uses. The n8n vs Make comparison on the site sets out those criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations