Resources · Make integration

Pointerpro (AU) Make integrationAutomate Pointerpro (AU) with Make.

Can a new survey response in Pointerpro update a contact on its own? The Pointerpro (AU) Make integration gives you 2 modules: 1 trigger and 1 action. This guide shows how to link your account, build a first scenario and pick the right module.

Try the Pointerpro (AU) integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Pointerpro (AU) Make integration do?

The Pointerpro (AU) Make integration lets Make, a no-code automation tool, react to survey responses and keep contacts in Pointerpro up to date. You build a scenario, the automation itself, from modules: small bricks that each watch for something or do one thing in your account.

With only two modules, the catalog is short, and that makes it easy to learn. The first useful setup is a response-to-contact flow that stays inside Pointerpro: Watch Response Event picks up new responses, then Upsert a Contact writes the respondent into your contact list. A consultant who runs assessments for clients can keep every respondent on file without copying names by hand.

The second pattern points outward. Responses picked up by the trigger can travel to any other app Make supports, such as a CRM, a spreadsheet or a chat tool. Picture a training provider who wants each completed questionnaire posted to a team channel for follow-up.

The third pattern starts elsewhere. A signup captured in another tool, a form or a booking app, can feed Upsert a Contact so Pointerpro knows the person before you send the next survey. The 123FormBuilder Make integration is one example of such a source.

Know the limits before you start. The Make documentation for Pointerpro (AU) is marked as limited: it lists the modules but does not describe their fields. There is also no Make an API Call module for this app, so anything beyond these two modules needs another route. If Make is new to you, the Make training covers the editor from scratch, and the n8n vs Make comparison helps if you are still choosing a tool.

Connect

How do you connect Pointerpro (AU) to Make?

  1. 01

    Add a Pointerpro (AU) module

    In your scenario, search for Pointerpro (AU), pick either module and click Create a connection. A connection is your Pointerpro account linked to Make once, then reused by both modules.

  2. 02

    Name the connection

    Giving the connection a name is optional, but it helps when you manage more than one Pointerpro account. Something like the team or client name makes it easy to pick the right one later.

  3. 03

    Authorize and save

    Approve Make on the Pointerpro page that opens, or paste the key Pointerpro gives you if the window asks for one. Then click Save, and the connection appears in the module.

First scenario

Your first scenario with Pointerpro (AU)

GoalWhen a new response event appears in Pointerpro (AU), Make adds or refreshes the matching contact.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the large + in the middle of the canvas to place the first module.

  2. 02

    Place the trigger

    Search for Pointerpro (AU), choose Watch Response Event and select your connection. Fill in what the module asks for; Make lists the options it can read once the connection exists.

  3. 03

    Add the contact step

    Click the + on the right of the trigger and add Upsert a Contact. Map the respondent details from the trigger into the contact fields shown by the module.

  4. 04

    Test with Run once

    Submit a test response in Pointerpro, then click Run once. Open the bubbles above each module to read the bundles, the items passed from one module to the next.

  5. 05

    Schedule and switch on

    Click the clock on the trigger to set how often Make checks, every 15 minutes by default, then switch the scenario on so it runs without you.

Triggers

What starts a Pointerpro (AU) scenario

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

Pointerpro (AU)1Watch Response Event

Watch Response Event

triggerIn the docs only

This trigger gives your scenario a starting point each time Pointerpro records a response event, so the data from a survey can move on to other modules without any export. Each event arrives as a bundle, one item the next module can use.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, and at 15 minutes at the shortest on the Free plan.
When to use it
whenever a completed assessment should lead somewhere, a contact update, a message to a colleague or a row in a sheet.
Watch out
the documentation does not describe this module, and its type is read from its name, so test it with Run once before you rely on it.
Modules

What Pointerpro (AU) can do in Make

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

Pointerpro (AU)1

Upsert a Contact

ActionIn the docs only

This action keeps one contact in Pointerpro in line with the data you send it. In common usage, an upsert creates the record when it is missing and updates it when it exists; the Make documentation does not confirm the exact matching rule.

When to use it
after a response or a signup in another tool, when you want Pointerpro to know the person before the next survey.
Watch out
run a test on a sample contact first, since the documentation lists no fields for this module.
Need help

Need help automating Pointerpro (AU) with Make?

A person reads every message.

FAQ

Pointerpro (AU) and Make: common questions

01Is the Pointerpro (AU) Make integration free?
Yes, on the Make side. Pointerpro (AU) is a standard app, available from the Free plan. The Free plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes per execution. Make counts usage in operations, one module running on one bundle. Your Pointerpro subscription is a separate matter.
02What do you need to connect Pointerpro (AU) to Make?
A Pointerpro (AU) account and a Make account. The documentation lists no other prerequisite and no app-specific steps, so the standard flow applies: add a Pointerpro module, click Create a connection, name it if you like, then approve Make on the Pointerpro page or paste the key the app gives you, and click Save. The connection is stored once and both modules reuse it. If the window asks for a detail you cannot locate, your Pointerpro account admin is the right person to ask.
03Does the Pointerpro (AU) trigger in Make work in real time?
No. Watch Response Event is listed as a scheduled trigger (the documentation does not describe it, so its type is read from its name): Make checks Pointerpro at the interval set on the scenario, every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval allowed; paid plans can go down to 1 minute. A response recorded just after a check is picked up at the next one. Pointerpro (AU) has no instant trigger in Make, so there is no webhook-based option for this app.
04What if a Pointerpro (AU) module is missing in Make?
It depends on what you need. The app has two modules, Watch Response Event and Upsert a Contact, and no Make an API Call module, so you cannot reach other parts of Pointerpro from this integration. The documentation is also marked as limited. If your use case goes further, look at whether another app in your stack can handle that step, or ask a Make agency to review the setup with you.
05Make or n8n for Pointerpro (AU)?
It depends on the criteria that matter to you, and this page only states facts about Make. In Make, Pointerpro (AU) offers one scheduled trigger and one contact action, runs from the Free plan and has no API call module. The same app may also exist as an n8n node; check that tool's own catalog for what it offers. Compare the modules each side gives you for your exact workflow, then test both on a small scenario before you commit.
Same platform

Other docs you might need on this stack.

Browse all integrations