Piggy + StackGo

Piggy and the compliance workflow around it.

Piggy publishes 6 trigger events and 9 actions on its public Zapier listing. That is what a StackGo connector would be built on.

Marketing Before the workflow Not connected yet
What Piggy is

Piggy is a SaaS Loyalty platform. Create your own loyalty program and reward your customers.

Description supplied by Piggy.

Where it fits

Before the workflow starts

Marketing systems hold people who are not clients yet. Compliance obligations begin at the moment one becomes a client, so this sits just upstream of the first step. The handover is the part worth getting right.

A check can start from
  • Contact Updated
  • New Contact
What StackGo sends to Piggy

An outcome, never the client’s identity data. Piggy would be told what happened; the verification detail stays in your system of record.

  • What happened
  • Who it was for
  • When
  • Where the record is

Personal fields are off by default. What goes back to your CRM explains the default; what each field holds is set out in what “integrates with” actually means.

Everything else Piggy publishes

Piggy’s public integration surface

The rest of what Piggy exposes on Zapier, beyond the ones above. This is the raw material a connector would use.

4 more events
  • New Credit Reception
  • New Reward Reception
  • Voucher Created
  • Voucher Redeemed
9 actions
  • Calculate Credits
  • Create Batch of Vouchers
  • Create Contact by Email Address
  • Create Contact Attribute
  • Create Credit Reception
  • Create Promotion
  • Create Voucher
  • Find or Create Contact by Email Address
  • Update Contact Attribute(s)

Names are Piggy’s own, read from its public Zapier listing on 23 October 2026.

Questions

Common questions about Piggy

Which Piggy events can start a compliance check?

“Contact Updated”, “New Contact”. These are Piggy’s own trigger names from its public Zapier listing. StackGo does not connect to Piggy yet, so they show where a connector would start.

Questions taken from what people actually search in Australia. We answer only the ones our own data answers.

Where this sits

Piggy sits beside the work, not inside it.

The compliance work happens in the five workflows below. Piggy is where a check can start, or where the result lands.

Want Piggy connected?

Requests decide the build order. Tell us and we will tell you where it sits.

Request this integration

Ready to make onboarding minutes, not hours?

Start free and run your first check today, or book a demo and we will walk you through it.

Cookie settings

Choose which optional cookies we can use. You can change this at any time from Cookie settings at the bottom of every page.