> ## Documentation Index
> Fetch the complete documentation index at: https://developers.perkstar.co.uk/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Perkstar to Make

> Get private-beta access, authorise Perkstar with OAuth, and test a controlled first Make scenario.

The private-beta app uses Perkstar OAuth. The person creating the connection
signs in to Perkstar, confirms the intended business, reviews the requested
access, and approves it. Make receives revocable OAuth tokens; the builder is
never asked to paste a Perkstar API key into a scenario.

<Warning>
  Perkstar for Make is not yet public in Make's app catalogue. Use only the
  private app access supplied by Perkstar. A similarly named app or setup page
  that asks for a raw Perkstar API key is not the official connection flow.
</Warning>

## Before you connect

* The Perkstar business is on Growth, Scale, Enterprise, or Franchise.
* Perkstar has enabled the intended Make organisation for the private beta.
* You can sign in to both the intended Perkstar and Make accounts.
* Your Perkstar role can connect integrations for the business.
* Your Make role can create connections and edit scenarios in the intended
  team.
* At least one active loyalty card exists for card-aware modules and filters.
* You know who will own the scenario and which customer fields each destination
  needs.

<Note>
  One Make connection represents one Perkstar business. Create a separately
  named connection for every business; a connection never searches or writes
  across Perkstar tenants.
</Note>

## Create the connection

<Steps>
  <Step title="Open the private-beta app">
    Sign in to the Make organisation that Perkstar enabled and create or open a
    scenario in the correct team. Add a module, search for **Perkstar**, and
    select a trigger, action, or search. Beta access makes the private app
    available to that organisation; it does not publish the app or activate a
    scenario.
  </Step>

  <Step title="Add a Perkstar connection">
    In the module's **Connection** field, choose **Add**. Make opens Perkstar's
    hosted authorisation page over HTTPS.
  </Step>

  <Step title="Confirm the business">
    Check the business and signed-in account shown by Perkstar. If either is
    wrong, cancel and switch Perkstar organisation before approving. Do not
    authorise first and rely on a later module filter to isolate another
    business.
  </Step>

  <Step title="Review and allow access">
    Read the plain-language permissions and choose **Allow** only if they match
    the intended scenario. The private-beta app requests customer, enrolment,
    card, event, webhook, marketplace-loyalty, and Wallet-push permissions used
    by its guided modules. If the connection offers **Advanced API scopes**,
    leave them unselected unless a documented **Make an API call** operation
    requires one; each selected scope appears on the Perkstar consent screen.
    Perkstar returns the connection to Make without displaying an API key.
  </Step>

  <Step title="Name and verify the connection">
    Use a name that identifies the tenant, for example `Perkstar — North Street
            Coffee (Live)`. Open the module again and confirm card selectors and a safe
    search return data only from that business.
  </Step>
</Steps>

The Make OAuth client allows five optional advanced scopes for documented
enrolment writes, transaction reads/writes, app-owned webhook reads, and
location reads. They are not part of an ordinary guided connection. Read
[OAuth permissions](/integrations/make/data-security#oauth-permissions) before
requesting one. Adding a scope later requires renewed consent; Make cannot add
it silently to an existing grant.

## Test a read-only scenario first

<Steps>
  <Step title="Add Search customers">
    Select **Search customers**, choose the new connection, and use an
    authorised internal test customer's exact email, phone, external reference,
    or pass barcode/serial. You can also filter by **Created after**. Use a
    narrow Limit for this connection test; Customer ID is not an input to this
    search module.
  </Step>

  <Step title="Run once">
    Choose **Run once** in Make. Open the module's output bundle and confirm the
    customer ID and business-owned fields are the expected record. A no-match
    result is not permission to guess another tenant's identifier.
  </Step>

  <Step title="Add one narrow destination">
    Map only the fields a low-risk destination step needs. Keep the scenario
    inactive until its filters, error handler, access, and data retention have
    been reviewed.
  </Step>
</Steps>

## Test the instant trigger

<Steps>
  <Step title="Start with Watch loyalty events">
    Add **Watch loyalty events** as the first module, create its attached
    webhook, and select one event. Choose a Card only when that event carries a
    Card ID and the scenario belongs to a single programme. Leave test events
    excluded unless this is an isolated test scenario.
  </Step>

  <Step title="Listen before creating the event">
    Choose **Run once**, then perform the exact low-risk event in the connected
    Perkstar business. A generic `webhook.test` diagnostic does not satisfy the
    module's business-event selection.
  </Step>

  <Step title="Inspect the bundle">
    Confirm the trigger's authenticated Perkstar verification request succeeded,
    then inspect the stable outer Event ID, dotted Event Type, Created
    timestamp, Organization ID, and nested Event Data before mapping another
    module. Optional Event Data fields can be absent or `null`.
  </Step>

  <Step title="Activate gradually">
    Add filters and an error handler, save the scenario, then schedule it **On**
    for one event/card and a narrow audience. Monitor Make scenario history,
    incomplete executions, and the corresponding Perkstar records before
    widening it.
  </Step>
</Steps>

## Connection and webhook lifecycle

| Change                          | Effect                                                                                                                                                                                    |
| ------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Rename a connection             | Changes its Make label only; the OAuth grant remains bound to the same Perkstar business.                                                                                                 |
| Reauthorise a connection        | Future modules use the renewed OAuth grant. Retest every active scenario that uses it.                                                                                                    |
| Revoke access in Perkstar       | Future API calls fail and app-owned subscriptions can no longer be managed until a valid connection is restored.                                                                          |
| Turn a scenario off             | Stops normal scenario processing, but does not necessarily delete its attached Make webhook. Check the scenario and Make webhook queue before assuming the Perkstar subscription is gone. |
| Delete the attached webhook     | The app's detach step deletes the corresponding app-managed Perkstar subscription. Historical Make executions remain under Make's retention settings.                                     |
| Delete a destination connection | Does not remove records the scenario already copied into that destination.                                                                                                                |

To revoke Perkstar access, open **Settings → Authorised apps** in the connected
Perkstar business and revoke the Make connection. Then remove or reauthorise the
connection in Make before reactivating affected scenarios.

Read [Webhooks and instant scenarios](/integrations/make/webhooks) before using
an event trigger, [Troubleshooting](/integrations/make/troubleshooting) before
reconnecting a shared production connection, and [Data and
security](/integrations/make/data-security) before mapping personal data.


## Related topics

- [Make troubleshooting](/integrations/make/troubleshooting.md)
- [Connect Perkstar to Zapier](/integrations/zapier/setup.md)
- [Make](/integrations/make/index.md)
- [Connect Odoo](/guides/odoo.md)
- [Connect with MCP](/tools/mcp.md)