Skip to main content
Make Connect Perkstar loyalty activity to the applications in a Make scenario. The app has one dynamic Watch loyalty events instant trigger with 29 event choices, 11 guided actions, two searches, and the required Make an API call universal module. Card and event selectors load choices from the connected Perkstar business, so builders normally map names and IDs without copying raw API requests.
The official Perkstar app for Make is currently a private beta. It is not published in Make’s public app catalogue. Access must be enabled by Perkstar for the intended Make organisation; finding a similarly named public app or being on an eligible Perkstar plan does not grant beta access.

Connect securely

Authorise one Perkstar business with OAuth. Do not paste an API key into a scenario or share one with a contractor.

Watch 29 events

Choose one loyalty event per instant module, with optional card and live/test filtering where supported.

Write safely

Use guided modules, stable source IDs, idempotent retries, and explicit consent checks in production scenarios.

Availability

Private-beta access and plan eligibility are separate. An eligible business still needs explicit beta access until Perkstar completes Make review and publishes the app.

Module map

The guided actions cover customer creation and updates, explicit find-or-create and find-or-enrol flows, loyalty earning and redemption, transaction reversal, and consented Wallet pushes. Make an API call is for supported public v1 operations that do not yet have a guided module; it does not bypass OAuth scopes, tenant boundaries, plan checks, validation, or consent.

What stays authoritative

Perkstar remains the system of record for customers, enrolments, Wallet passes, loyalty balances, rewards, and outbound events. Make stores scenario configuration, execution records, webhook queues, and any values copied into other modules. Perkstar cannot inspect or control later modules in a scenario. The business is responsible for the destination app, mappings, lawful purpose, access, retention, and deletion of copied customer data. Read Data and security before processing personal data or sending marketing messages.

Start here

Set up the connection

Review private-beta prerequisites, approve OAuth, and run a controlled first scenario.

Browse all modules

See every event choice, guided action, search, required input, and important boundary.

Understand webhooks

Learn subscription lifecycle, server-attested delivery verification, retries, duplicate protection, and queues.

Troubleshoot a scenario

Diagnose access, OAuth, trigger, module, rate-limit, consent, and incomplete execution failures without exposing secrets.
Beta questions are handled through support@perkstar.co.uk. Include the Perkstar business name and approximate UTC time, but never send an OAuth token, Make webhook URL, customer payload, or unredacted execution screenshot.