Resources · Make integration

SurveyTale Make integrationAutomate SurveyTale with Make.

What happens to a survey answer once it lands in SurveyTale? The SurveyTale Make integration gives you 3 triggers and 1 API Call module to pass each response on. This page shows how to connect your account and build a first scenario.

Try the SurveyTale integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SurveyTale Make integration do for you?

The SurveyTale Make integration lets Make notice survey responses and hand them to the rest of your stack. A scenario is the automation you build in Make, a chain of modules; each module is one brick, such as a trigger that starts things or an action that does something. Here you get three triggers around responses and one module that reaches the SurveyTale API.

Only completed answers reach your team. Put Watch Survey Response Finished at the start and each finished response becomes a bundle, one item flowing to the next module, that you can drop into a spreadsheet, a CRM or a chat app. Half-filled surveys stay out of the way.

Follow a survey from the first click. Watch Survey Response Created picks up new responses at each scheduled check, which suits a support desk that wants to see who started a feedback form, even before the last question.

Keep a copy in sync when people change their minds. Watch Survey Response Updated catches edits to an existing response, so the record you pushed elsewhere does not drift away from what the respondent actually said.

Know the limits before you plan. Make itself states it cannot yet offer complete documentation for SurveyTale because too little public information exists, so the module list is short and field details are not described. When you need something the triggers do not cover, Make an API Call reaches the SurveyTale API with the same connection. SurveyTale may also have an n8n node; the n8n vs Make comparison helps you pick an editor, and the Make pricing page explains how operations are counted. If you are new to the editor, Make training covers the basics.

Connect

How do you connect SurveyTale to Make?

  1. 01

    Add a SurveyTale module

    In a new scenario, click the +, search for SurveyTale and pick any of its modules. Then click Create a connection: a connection is your SurveyTale account linked to Make once and reused by every SurveyTale module.

  2. 02

    Name it and authorize

    Give the connection a name if you like, handy when a colleague later adds a second account. Then authorize Make on the SurveyTale page that opens, or paste the key SurveyTale gives you, depending on what the connection window asks for.

  3. 03

    Save and check the list

    Click Save. The connection now appears in the module's dropdown, and every other SurveyTale module you add later will offer it without asking you to sign in again.

First scenario

Your first scenario with SurveyTale

GoalWhen a respondent finishes a survey in SurveyTale, Make passes that response to a SurveyTale API request you define.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + in the middle of the editor to add your first module.

  2. 02

    Add the trigger

    Search for SurveyTale and choose Watch Survey Response Finished. Pick your connection, or create one as shown above, then fill the fields Make shows you.

  3. 03

    Chain the API Call

    Click the + to the right of the trigger and add Make an API Call. Map values from the response bundle into the request you build from the SurveyTale API reference.

  4. 04

    Test with Run once

    Finish a test survey yourself, then click Run once. Open the bubbles above each module to read the bundles they received and confirm the data looks right.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set how often Make checks; a new scenario runs every 15 minutes by default. Then turn the scenario on.

Triggers

SurveyTale triggers in Make

3 modules start a scenario when something happens in SurveyTale. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by SurveyTale as soon as it happens.

SurveyTale1Watch Survey Response Created

Watch Survey Response Created

triggerIn the docs only

This trigger hands you each new response SurveyTale has recorded at the next scheduled check, not only the finished ones. You see activity early instead of waiting for the final answer.

How it fires
scheduled, so Make checks the app on the scenario's schedule. The docs do not mark it as instant, which is why it is treated as scheduled here.
When to use it
a team wants to know that someone opened a feedback form, for example to spot where people give up.
Watch out
a response picked up here may still be incomplete.
SurveyTale2Watch Survey Response Finished

Watch Survey Response Finished

triggerIn the docs only

Pick this one when you only care about answers people actually sent to the end. Each completed response starts your scenario once, so the next modules work on full data.

How it fires
scheduled; Make checks the app on the scenario's schedule, based on the module name rather than an explicit mention in the docs.
When to use it
a finished customer satisfaction survey should create a row in a sheet or a ticket for the account manager.
Watch out
field details are not documented, so run the scenario once and inspect the bundle before mapping.
SurveyTale3Watch Survey Response Updated

Watch Survey Response Updated

triggerIn the docs only

Changes made to a response that already exists come through here, which keeps any copy you store elsewhere aligned with the latest version of the answers.

How it fires
scheduled, as far as the module name suggests: Make checks the app on the scenario's schedule rather than waiting for a webhook.
When to use it
you already push responses into a CRM and want an edited answer to overwrite the old value there.
Watch out
the docs do not say which edits count, so test with a real change and Run once before relying on it.
Modules

Other SurveyTale modules

SurveyTale gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

SurveyTale1

Make an API Call

ActionIn the docs only

This module sends your own request to the SurveyTale API, reusing the connection you already created, so anything the three triggers leave out is still within reach.

When to use it
you need data or an action that no listed module offers, and the SurveyTale API reference describes the endpoint.
Watch out
you build the request yourself, and Make has little public documentation on SurveyTale to guide you.
Need help

Need help automating SurveyTale with Make?

A person reads every message.

FAQ

SurveyTale and Make: common questions

01Is the SurveyTale Make integration free?
Yes, SurveyTale is a standard app, so it is available from the Free plan. That plan lets you keep 2 scenarios active, run scheduled scenarios at most every 15 minutes, and caps each run at 5 minutes, with files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and allow unlimited active scenarios. Make counts usage in credits, one operation per module run on a bundle, so a busy survey spends more of your monthly allowance than a quiet one.
02What do you need to connect SurveyTale to Make?
A SurveyTale account and a Make account. The Make documentation lists no specific prerequisite and no official connection steps for SurveyTale, so you follow the usual path: add a SurveyTale module, click Create a connection, optionally name it, authorize Make on the SurveyTale page or paste the key SurveyTale gives you, and click Save. That connection is then reused by every SurveyTale module in all your scenarios, so you only do this once per account.
03Does the SurveyTale trigger fire in real time?
No, not as far as the documentation shows. None of the three SurveyTale triggers is marked as instant, so they are treated as scheduled: Make checks SurveyTale when the scenario's schedule comes around, every 15 minutes by default, or every minute at best on a paid plan. Responses that arrived in between are picked up together at the next check. An instant trigger would need SurveyTale to call Make through a webhook, and the documentation does not list one for this app.
04What if the SurveyTale module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the SurveyTale API with the same connection as the triggers, so it covers what the listed modules do not. Make warns that it cannot yet provide complete documentation for SurveyTale because there is not enough public information about the app, which means you will rely on the SurveyTale API reference to build the request. Test it with Run once and read the returned bundle before you switch the scenario on.
05Should you use Make or n8n for SurveyTale?
It depends on which editor you already know and where the rest of your automations run. On Make, SurveyTale offers three scheduled triggers and an API Call module, available from the Free plan. SurveyTale often has an n8n node as well, so check what that node covers against the modules you need. Neither choice changes what the SurveyTale API itself can do; the deciding factor is usually the tool your team is comfortable maintaining over time.
Same platform

Other docs you might need on this stack.

Browse all integrations