Skip to main content
Start with Zap history and the connected Perkstar business. Record the step name, event or request time, status, and any Perkstar X-Request-Id before retrying. Never copy an OAuth token, unique hook target URL, or full customer payload into a support message.

​
Connection and access

Open the official public Beta listing, confirm you are signed in to the intended Zapier account, and search for Perkstar rather than a similarly named app. You can also use App connections → Add connection. No invitation is required. If a managed Zapier workspace restricts apps, ask its administrator to allow Perkstar.
The public listing does not create or join a Perkstar business. If you are an existing team member, accept the Perkstar team invitation sent to your exact email address and sign in with that account before reconnecting. Do not create a second business just to authorise Zapier. If you are a new customer, finish Perkstar account and plan setup first.
Zapier is available to Growth, Scale, Enterprise, and Franchise businesses. Confirm the current Perkstar plan and that you are connecting the intended business. Free and Starter businesses must upgrade before connecting.
Cancel instead of approving. Sign out or switch to the correct Perkstar organisation, then start the connection again. One connected account is tenant-scoped to one business.
One connected account is scoped to one Perkstar business, but it can be reused across many Zaps. Add a separate Perkstar connection for each other business and give each connection a clear name. A Zapier account can hold multiple Perkstar connections.
Reauthorise the Perkstar connected account in Zapier, then test every enabled Zap that uses it. If access was revoked in Perkstar, a new approval is required; retrying the old task does not restore the grant.

​
Instant triggers

Confirm the Zap uses the correct Perkstar business and named event. Start the Zapier test/listen step first, then perform that exact event. If a card filter is present, confirm the event belongs to the selected active card. The diagnostic webhook.test event does not satisfy a business-event trigger.
Check that the Zap is published and enabled, the connected account is still authorised, and the expected Perkstar business event actually completed. Inspect Zap history. Perkstar keeps app-managed delivery attempts out of the custom-webhook dashboard so their callback URL and signing secret cannot be changed behind Zapier’s back; quote the event time and ID to Perkstar support if Zap history is not enough.
Automatic retries keep one logical delivery ID and should deduplicate. Confirm the runs have the same trigger id. Protect destination writes with the Perkstar ID or another stable source reference.
This is allowed. Compare the event-specific occurredAt timestamp and the destination’s current state. The exposed event_created_at field expresses that same source-event time in ISO 8601; the internal signing timestamp is the delivery-attempt time.
Documented optional mapping fields can be null when they do not apply, and trigger bodies are not automatically enriched with a customer profile. Review the event catalogue, guard optional mappings, and add Find Customer or Find Enrolment or Pass only when current state is appropriate.
Creating a pass or opening its save link is not installation evidence. Apple normally reports installation through its device callback. Google is observed periodically; recently issued passes are eligible on the 15-minute projector, while object age, provider cadence, and projector backlog can extend the delay. Check the Zap and pass again after a later completed sweep rather than treating 15 minutes as an SLA. The trigger fires only for the first observed install of that pass. A business’s first Google-install trigger uses its first check as a no-event baseline; tracking begins after that warm-up, so enable and test the Zap before distributing install links.
Card Scanned covers successful online Perkstar Scanner lookups only. A lookup served solely from the scanner’s offline cache never reaches the webhook boundary and does not fire this trigger. Dashboard searches and POS customer lookups are also excluded.
The trigger reports movement between Perkstar’s six exclusive lifecycle groups, not entry into or exit from an operator-created saved segment. A customer’s first classification is stored as a baseline without an event, preventing a new Zap from replaying the entire customer base. For the first interested trigger in a business, allow one completed periodic sweep to establish that baseline before expecting later transitions.
The event belongs to one enrolment and one effective expiry instant. If the enrolment is extended or reissued and later reaches a different expiry, another event is expected. Use enrollmentId plus expiresAt as the business identity when the destination needs its own duplicate protection.
This trigger is customer-to-customer loyalty activity. It includes both the referrer’s and referred customer’s IDs, but it does not represent an agency, merchant, partner, or affiliate invitation.

​
Searches and actions

​
Safe replay

Before retrying or manually replaying a failed task:
  1. Decide whether the earlier action may already have succeeded.
  2. Keep the same source ID field value. Perkstar recreates the same action-specific external transaction ID, including its deterministic hash form when needed.
  3. Fix a non-retryable validation, permission, or consent error first.
  4. Retry from Zapier once and inspect the returned Perkstar record.
  5. Replay once, then inspect the result before trying again.
To reverse a Zapier loyalty write, prefer its returned Perkstar Transaction ID. If only the original source ID is available, select Original Source Transaction ID and the exact Perkstar action that recorded it. If mapping the returned External Transaction ID, map it exactly without removing the zapier: namespace.

​
Ask for help

For a problem in a Zap workflow, use Zapier Support first. That route preserves the Zap and run context for Zapier’s first-line troubleshooting; Zapier will escalate an actionable Perkstar integration report to us when needed. Contact Perkstar Support directly for a Perkstar account, plan, team invitation, business-selection, or OAuth-consent problem. For a support request, keep the failed run in Zap history and include:
  • the Perkstar business name;
  • the Zapier trigger, action, or search name;
  • the approximate UTC time and Zap run/task ID;
  • the Perkstar X-Request-Id, event ID, or delivery ID when available; and
  • the status/code with secrets and personal fields removed.
Do not delete the failed history before support has finished tracing it. Never send a password, OAuth token, refresh token, webhook target URL, or full customer payload. For suspected exposure or a personal-data incident, contact privacy@perkstar.co.uk immediately.

Related topics

Zapier data and securityZapierZapier recipesConnect Perkstar to ZapierChangelog