Resources · Make integration

Pointerpro Make integrationAutomate Pointerpro with Make.

Every survey response can start work somewhere else without a single copy and paste. The Pointerpro Make integration gives you 2 modules: one instant trigger and one action. This page is for teams running surveys who want to connect their account, build a first scenario and know what each module does.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Pointerpro Make integration do for you?

The Pointerpro Make integration links your Pointerpro account to Make, a visual tool where you chain apps together without writing code. Pointerpro can tell Make the moment a response event happens, and Make can create or refresh a contact in Pointerpro. Everything else happens in the apps you connect next.

Responses that reach your team right away. Watch Response Event fires as soon as someone answers. A scenario (the automation you build in Make) can pass that answer to the next module, for example a row in a spreadsheet or a message to the person who follows up.

A contact list that stays clean. Upsert a Contact creates the person in Pointerpro when they are new and updates them when they already exist. Feed it from a signup form or a CRM and you avoid duplicates before your next survey goes out.

Survey data inside the rest of your stack. Sales can see how a prospect answered, support can spot unhappy customers, marketing can segment a list. Each case starts with the same trigger and ends in the app that team already uses. The 123FormBuilder Make integration covers a similar need on the form side.

What Make does not give you here: only these two modules exist, and Make states that its Pointerpro documentation is limited because little public information is available. There is also no Make an API Call module for this app. If you are weighing tools, the n8n vs Make comparison helps, and the Make training teaches the editor from scratch.

Connect

How do you connect Pointerpro to Make?

  1. 01

    Add a Pointerpro module

    In a scenario, click the + and search for Pointerpro, then pick a module. Make asks for a connection, meaning your Pointerpro account linked to Make once and reused by every Pointerpro module. Click Create a connection.

  2. 02

    Name the connection

    Giving the connection a name is optional, but it helps when several accounts or clients live in the same Make workspace. Pick something you will recognize later, such as the team or the account owner.

  3. 03

    Authorize and save

    Depending on what Pointerpro asks, you either approve Make on the Pointerpro page or paste the key that Pointerpro gives you. Then click Save, and the connection appears in the module, ready to use.

First scenario

Your first scenario with Pointerpro

GoalWhen a new response event happens in Pointerpro, Make saves the respondent as a contact with Upsert a Contact.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the + in the middle of the canvas. This first slot is where the trigger goes, the module that starts everything.

  2. 02

    Add Watch Response Event

    Search for Pointerpro, choose Watch Response Event and click Create a connection (or pick the one you already have). The lightning badge tells you it is an instant trigger.

  3. 03

    Add Upsert a Contact

    Click the + on the right of the trigger and pick Upsert a Contact, reusing the same connection. If the response event carries the respondent's details (the test will show you), map them into its fields so each answer feeds your list.

  4. 04

    Test with Run once

    Click Run once, then submit a test response in Pointerpro. Each module shows the bundles it received, a bundle being one item passed along, here one response event.

  5. 05

    Switch it on

    When the test looks right, save and turn the scenario on. From then on, every new response event starts the scenario without you opening Make.

Triggers

What starts a Pointerpro scenario

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

Pointerpro1Watch Response Event

Watch Response Event

Instant trigger

In Make“Triggers when a new response event occurs.”

Watch Response Event gives your scenario a starting point the moment a new response event occurs in Pointerpro: it reaches Make and the next modules run on it.

How it fires
instant. Pointerpro calls Make through a webhook as soon as the event happens, so there is no polling schedule to tune.
When to use it
a lead answers a qualification survey and sales should see the answer without checking the dashboard.
Watch out
Make's documentation for this app is limited, so run a real test response with Run once before you rely on the data you map.
Modules

What Pointerpro can do in Make

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

Pointerpro1

Upsert a Contact

Action

In Make“Create contact if it does not already exist or updates them if they do.”

Upsert a Contact keeps your Pointerpro audience tidy: it creates the person when they are new and updates the existing record when they are already there, all in one module.

When to use it
a customer signs up in your shop or CRM and should be ready for the next survey, without anyone checking for duplicates by hand.
Watch out
each run counts as an operation, one execution of one module on one bundle, so filter out contacts you do not need upstream.
Need help

Need help automating Pointerpro with Make?

A person reads every message.

FAQ

Pointerpro and Make: common questions

01Is the Pointerpro Make integration free?
Yes, Pointerpro is a standard app in Make, so you can use it on the Free plan. That plan has limits: 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lift the interval to 1 minute and allow unlimited active scenarios. Usage is counted in operations, so every module run on a bundle uses part of your monthly allowance. Your Pointerpro subscription is a separate matter.
02What do you need to connect Pointerpro to Make?
A Pointerpro account and a Make account. Make's documentation lists no specific prerequisite for this app. You add a Pointerpro module, click Create a connection, optionally name it, then either authorize Make on the Pointerpro page or paste the key Pointerpro provides, and save. The same connection is then reused by both Pointerpro modules. Since Make notes that its documentation for this app is limited, keep someone with access to the Pointerpro account available during the first setup.
03Does the Pointerpro trigger in Make work in real time?
Yes. Watch Response Event is an instant trigger: Pointerpro calls Make through a webhook as soon as a response event happens, and the scenario starts right away. You do not wait for a polling interval like you would with a scheduled trigger. The lightning badge on the module in the editor confirms this. To check it end to end, click Run once in Make and submit a test response, then read the bundle the trigger received before switching the scenario on.
04What if a Pointerpro module is missing in Make?
It depends on what you need. Make offers only two Pointerpro modules, Watch Response Event and Upsert a Contact, and this app has no Make an API Call module to go beyond these two actions. Make also says its documentation for Pointerpro is limited. If your case goes further, another survey or form app in Make may cover it, or a Make specialist can review your setup and suggest a workable route.
05Should you use Make or n8n for Pointerpro?
It depends on your criteria rather than on a winner. Many apps available in Make also have a node in n8n, so first check whether Pointerpro does and whether the operations you need exist on both sides. In Make, you get an instant response trigger and a contact upsert, a visual editor, and a Free plan to test. Pick the tool your team already knows and can maintain. The comparison page on this site lays out the differences between the two platforms in more detail.