Resources · Zapier integration

Piggy Zapier integrationAutomate Piggy with Zapier.

The Piggy Zapier integration offers 6 triggers, 9 actions and 3 searches. Every trigger is instant, so a new member, a redeemed voucher or a claimed reward reaches your other tools right away, and the actions let those tools write contacts, credits and vouchers back into Piggy.

See the 18 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Piggy Zapier integration does

Piggy runs loyalty programs: members collect credits, claim rewards and use vouchers. Connecting it to Zapier links that program to the rest of your stack, so the shop, the newsletter and the CRM know what happens in Piggy, and can feed Piggy in return, without exports or copy-paste.

Three outcomes worth building. A welcome offer for every new member: New Contact starts the Zap, Create Voucher issues a voucher from an existing promotion, and your mail tool sends it. A clean customer file: each sign-up in a web shop or a form goes through Find or Create Contact by Email Address, so Piggy never gets the same person twice. And credits for purchases made outside Piggy: Find Contact by Email Address gets the member, then Create Credit Reception adds the credits to the right shop.

All six triggers are instant. Piggy tells Zapier about each event itself, so the interval of the free plan does not slow anything down: a redeemed voucher can show up in your sheet straight away.

What Zapier does not do here: there is no trigger for a member reaching a threshold or for a voucher about to expire, and no action deletes a contact, a voucher or a promotion. Several actions want a Contact UUID rather than an email, so many Zaps need a search step first, which makes them multi-step and therefore paid.

Comparing platforms before you commit? The Make vs Zapier comparison is worth a look.

Vocabulary

The Zapier words used on this page

Eight terms, one line each, before the details.

Zap
The automation you build in Zapier: one trigger, then one or more actions that run every time that trigger event happens.
Trigger
The event in an app that starts the Zap. Piggy has six, from a new contact to a redeemed voucher.
Action
What the Zap does once started: the step that writes something for you, such as a contact or a voucher in Piggy.
Task
The unit Zapier bills: one action completed successfully. The monthly count on your plan is a count of those.
Instant vs polling trigger
An instant trigger is reported by the app the moment it happens. A polling one is checked on a timer. All Piggy triggers are instant.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
Search step
A step that looks up something that already exists, such as a Piggy contact, so the next steps can use what it found.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action, a filter or a search makes it one, and it then needs a paid plan.
Cost

What Piggy on Zapier really costs

Piggy is not a premium app, so it works on the free plan. Zapier counts tasks, and only on actions that succeed.

  • Premium appNo, works on the free plan
  • Free plan100 tasks a month, two-step Zaps
  • Piggy event received0 tasks
  • TriggersAll 6 instant, the grid does not apply

A Piggy event starting a Zap costs nothing: the trigger never uses a task. Each action that completes counts one, whether it writes into Piggy or into another app, and a failed one is not counted. A few apps and actions take more than one task, so check the counter after the first runs. The free plan gives 100 tasks a month and two-step Zaps. The moment you add a search step, a filter or a second action (which any Zap feeding Calculate Credits, Create Credit Reception or Update Contact Attribute(s) usually needs, because of the Contact UUID), the Zap is multi-step and needs a paid plan.

Connect

Connect your Piggy account in three steps

  1. 01

    Open the Apps page

    In Zapier, go to the Apps page of your account and click + Add connection. You need a Piggy account, plus access to any shop or program you do not own but want the Zap to use.

  2. 02

    Pick Piggy

    Search for Piggy in the dialog, select it and click Add connection. A new tab opens on the Piggy side, where you sign in with the account that runs your loyalty program.

  3. 03

    Sign in and grant access

    Log in to Piggy in that tab and allow Zapier to access the account. The connection is saved once and offered in every Piggy step you add afterwards, trigger, action or search.

First Zap

Your first Zap: a welcome voucher for every new member

GoalEach new Piggy contact gets a voucher from the welcome promotion, sent by email.

  1. 01

    Build: Piggy starts it

    Create a Zap, choose Piggy and the New Contact event, then select your Piggy connection. Since it is instant, no plan interval applies.

  2. 02

    Test the trigger

    Run the test: Zapier brings back the three most recent contacts of the account. Pick a real one so the email address and name you map later carry true values.

  3. 03

    Create the voucher

    Add Piggy with Create Voucher and choose the welcome promotion in Promotion uuid, the only required field. Run the step and read the voucher it returns.

  4. 04

    Send it by email

    Add your mail tool and its send action, map the contact's email address and the voucher details into the message. This second action makes the Zap multi-step, so paid.

  5. 05

    Test, then publish

    Test the email on an address you own, check what came back, then click Publish. From then on, each new member gets the voucher with no wait.

Triggers

The 6 Piggy triggers

6 events start a Zap when something happens in Piggy, and 6 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Contact Updated

Instant trigger

In Zapier“Triggers when an contact is updated.”

Starts your Zap whenever an existing member's record changes in Piggy, and passes along the contact as it now stands so other tools can catch up with the change.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
keeping your CRM or newsletter list in line with Piggy, so a member who updates their details is updated everywhere.
Watch out
pair it with Update Contact Attribute(s) in the same Zap and each update fires the trigger again, which loops and burns tasks.
2

New Contact

Instant trigger

In Zapier“Triggers when a new contact is created.”

Fires on each contact created in Piggy, whether someone joined the program or another Zap created them. It is the natural starting point for anything that should happen to new members.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a welcome voucher, a welcome email, or adding the member to your CRM.
Watch out
members who joined before the Zap was published are never picked up; handle the existing base separately.
3

New Credit Reception

Instant trigger

In Zapier“Triggers when a new credit reception is created.”

A credit reception is Piggy's record of credits given to a member. This trigger runs each time a new one is created, so every credit award can be logged or announced somewhere else.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a running log of credits in a spreadsheet, or a thank-you message after a purchase that earned credits.
Watch out
if the same Zap also runs Create Credit Reception, every award it makes starts it again.
4

New Reward Reception

Instant trigger

In Zapier“Triggers when new reward reception is claimed.”

Reacts when a member claims a reward. The Zap starts with that reward reception, which tells your team or your systems that something has to be handed over or prepared.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
alerting the store team in their chat, or creating a fulfilment task in your project tool when a physical reward is claimed.
Watch out
Zapier has no action to create a reward reception, so this flow only goes one way, out of Piggy.
5

Voucher Created

Instant trigger

In Zapier“Triggers when a voucher is created.”

Each voucher created in Piggy, one at a time or as part of a batch, starts the Zap with its details, ready to send, log or share.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
keeping a register of issued vouchers, or sending each voucher created by staff to its recipient.
Watch out
a batch of up to 500 vouchers means up to 500 runs at once, which Zapier's flood protection can hold back, and a Zap that calls Create Voucher itself would restart on every voucher it creates.
6

Voucher Redeemed

Instant trigger

In Zapier“Triggers when a voucher is redeemed”

Watches the moment a voucher is used. The Zap gets the redeemed voucher, which closes the loop between the offer you sent and the visit or order it produced.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
measuring which promotion actually brings people back, by adding each redemption to a sheet or a CRM record.
Watch out
redemptions made before the Zap was published are not sent; past results have to be exported from Piggy.
Actions

The 9 Piggy actions, grouped by job

Piggy gives you 9 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Calculate Credits

Action

In Zapier“Calculate how many credits would be issued if a credit reception was to be made with the given values.”

Works out how many credits a purchase would earn, without giving them. It needs the Contact UUID, the Shop UUID and a Unit value.

When to use it
showing a customer what they would earn, in a quote or a confirmation email, before anything is booked.
Watch out
nothing is credited; to actually award the credits, add Create Credit Reception.
2

Create Batch of Vouchers

Action

In Zapier“Creates a batch of vouchers”

Generates many vouchers at once for one promotion. Besides the Promotion uuid, you set a Quantity between 1 and 500.

When to use it
a print run for an event or a partner who hands out codes in bulk.
Watch out
a Zap watching Voucher Created will receive the whole batch at once, which flood protection can hold back.
3

Create Contact by Email Address

Action

In Zapier“Creates new contact with email address.”

Adds a new member to Piggy from a single required field, Email address, which must be valid.

When to use it
a source you trust to send only new people, such as a dedicated sign-up form.
Watch out
if the person may already exist, the find-or-create action below is the safer choice.
4

Create Contact Attribute

Action

In Zapier“Create a new contact attribute.”

Extends your Piggy contacts with a new attribute, a field that every member can then carry. You name it and pick its Contact Attribute Data Type, both required.

When to use it
rarely in a recurring Zap; more often once, when another tool introduces a field Piggy should store.
Watch out
running it on every trigger tries to create the same attribute over and over.
5

Create Credit Reception

Action

In Zapier“Creates a new credit reception.”

Awards credits to a member in a given shop. The two required fields are the Contact UUID and the Shop UUID the credits go to.

When to use it
purchases made in a till or a web shop that Piggy does not see on its own.
Watch out
the shop must exist in Piggy first, and the contact's UUID must come from a search or an earlier step.
6

Create Promotion

Action

In Zapier“Creates a new Promotion”

Sets up a new promotion in Piggy, the container that vouchers are issued from. It asks for a Name and a Description, both required.

When to use it
campaigns planned in another tool, where each new campaign should have its promotion ready in Piggy.
Watch out
a promotion alone sends nothing; vouchers are created in a separate step.
7

Create Voucher

Action

In Zapier“Creates a new voucher”

Issues one voucher from an existing promotion, chosen in Promotion uuid, the only required field.

When to use it
one voucher per event, such as a welcome offer for a new member or an apology after a complaint.
Watch out
it triggers Voucher Created, so never build both into the same Zap.
8

Find or Create Contact by Email Address

Action

In Zapier“Finds an existing contact or creates a new contact, with email address.”

Looks for a member by email and creates one only if nobody matches. One action, one required field, and no duplicate members in your program.

When to use it
web shop orders or form entries where returning customers and new ones arrive mixed together.
Watch out
it is an action, not a search step, so it counts as a task when it completes.
9

Update Contact Attribute(s)

Action

In Zapier“Update the value of attribute(s) of a contact.”

Changes the values stored on a member's record. You give the Contact UUID, then fill in the attributes to change in the fields below it.

When to use it
copying a birthday, a preferred store or a segment from your CRM into Piggy.
Watch out
it wants the UUID, not the email, so a search such as Find Contact by Email Address usually comes first.
Searches

The 3 Piggy searches

3 search steps look for data that already exists in Piggy, so a later step can use it.

A search step changes nothing in Piggy: it finds a member or a voucher that already exists and hands it to the next steps. In this app, that is mostly how a Zap gets the Contact UUID that several actions require. Three settings decide what happens when the result is not the expected one.

1

Find Contact by Email Address

Search

In Zapier“Finds contact by email address.”

Finds a member from their email address, the one required field, and returns the record with its UUID for the steps that follow.

When to use it
in front of Create Credit Reception, Calculate Credits or Update Contact Attribute(s), which all need the UUID.
Watch out
a misspelled or outdated email finds nobody and, by default, stops the Zap.
2

Find Voucher

Search

In Zapier“Finds a voucher by code”

Looks up a voucher by its Code, the unique code that identifies it in Piggy.

When to use it
a customer types a code in a form or at a till, and the Zap needs to know which voucher it is before going further.
Watch out
the code has to match exactly what Piggy issued, so map it rather than retyping it.
3

Get Contact by UUID

Search

In Zapier“Search contact by it's UUID .”

Fetches a member's full record from a Contact UUID you already have, from a trigger or an earlier step.

When to use it
a trigger hands over the UUID but the next step needs the email or other details of the member.
Watch out
without a UUID in hand, start with Find Contact by Email Address instead.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there, and the steps that depended on it are skipped. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    None of the three Piggy searches offers this box. To create a missing member, use the Find or Create Contact by Email Address action instead.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one (the default), stop the Zap, or hand all of them on at once.
When it breaks

When a Piggy Zap breaks

Zapier attaches no help article to Piggy, and no limit specific to the app is on record. The traps below are the ones every Zap shares, and Piggy's mix of triggers and actions makes two of them easy to fall into.

  • A Zap that keeps triggering itself

    Voucher Created with Create Voucher, or Contact Updated with Update Contact Attribute(s): when a Zap writes where its own trigger watches, it restarts endlessly and drains your tasks.

  • Existing members are never processed

    A Zap only reacts to what happens after it is switched on. Members, vouchers and credits already in Piggy are not picked up; handling them is a separate job.

  • A voucher batch is held back

    A batch of up to 500 vouchers, or a bulk import of members, can return a huge burst of events, and Zapier's flood protection may hold those runs back.

  • A search finds nobody and the Zap stops

    By default, a search with no result stops the Zap and skips the steps that relied on it. Check the email or code being mapped before blaming Piggy.
Need help

Need help automating Piggy with Zapier?

A person reads every message.

FAQ

Piggy Zapier integration: frequent questions

01Is the Piggy Zapier integration free?
On the Zapier side, yes. Piggy is not a premium app, so it works on the free plan, which includes 100 tasks a month and two-step Zaps. That covers one Piggy trigger plus one action, or one trigger elsewhere plus one Piggy action. Many useful Piggy Zaps need more, because several actions want a Contact UUID that only a search step provides, and any search, filter or second action needs a paid plan. Your Piggy subscription is separate, and this page gives no price for either tool.
02How many tasks does a Piggy Zap use?
One task per action that completes, in Piggy or elsewhere. The trigger costs nothing. A Zap that logs each redeemed voucher in a sheet uses one task per redemption. A Zap that finds a member by email, then creates a credit reception, adds a search step and an action, so plan for the action at least. A failed action is not counted. A few apps and actions take more than one task, so check the counter after the first real runs.
03Does Piggy work in real time with Zapier?
Yes, on the trigger side. All six Piggy triggers are instant: Piggy tells Zapier about each event itself, so the Zap starts with no wait, whatever your plan. The interval grid for polling triggers (15 minutes on Free, 2 on Professional, 1 on Team and Enterprise) does not apply. In the editor, such Zaps show a lightning bolt. When Piggy is the action and another app starts the Zap, the speed depends on that other app's trigger.
04What do you need to connect Piggy to Zapier?
A Piggy account and a Zapier account. From the Apps page in Zapier, click + Add connection, search for Piggy, click Add connection, sign in to Piggy in the tab that opens and grant access. If the Zap must use shops or programs that belong to someone else, the connected account needs access to them. Before building credit or voucher Zaps, set up at least one shop and one promotion in Piggy, since those actions require their identifiers.
05Why do Piggy actions ask for a Contact UUID instead of an email?
Because Piggy identifies members by a unique ID, and Calculate Credits, Create Credit Reception and Update Contact Attribute(s) all require it. Most other apps only know the email. The fix is a search step before the action: Find Contact by Email Address returns the member with their UUID, which you then map into the field. If the trigger already carries the UUID, Get Contact by UUID fetches the rest. Either way, the Zap becomes multi-step and needs a paid plan.
06What if the Piggy operation you need does not exist?
Start from the list: 6 triggers on contacts, credits, rewards and vouchers, 9 actions to create contacts, attributes, credits, promotions and vouchers, and 3 searches. Nothing deletes a record, and nothing creates a reward reception from Zapier. If the missing piece is a check, such as a credit balance, a filter on data you already have may cover it. If it is a write Piggy does not expose here, it has to be done in Piggy itself.
07Zapier, Make or n8n for Piggy?
Decide on criteria, not on a ranking. On Zapier, Piggy works on the free plan for two-step Zaps, its six triggers are instant so events move with no wait even on that plan, and most Zaps that write credits or attributes need a search step, so a paid plan, with one task per completed action. Weigh that against how many loyalty events you expect each month, how many steps each one needs, and which of your other tools each platform already connects.
Same platform

Other docs you might need on this stack.

Browse all integrations