Piggy offers cashback and loyalty program integrations for online stores, letting users earn points or discounts and encouraging repeat purchases
Piggy offers cashback and loyalty program integrations for online stores, letting users earn points or discounts and encouraging repeat purchases On Nagent, Piggy is exposed as a fully-configurable marketing automation integration that any agent can call — 14 actions, and API key authentication. No code is required to wire Piggy into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Piggy to automate the kinds of tasks marketing automation teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Piggy into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Piggy, with input parameters and output schema. Drop these into any step of an agent built in Helix.
PIGGY_CLAIM_ANONYMOUS_CONTACTTool to claim an anonymous contact by associating it with a real email address. Use when converting an anonymous contact (with a fictional email) into a verified contact with a real email address.
Input parameters
The real email address for the Contact that is about to be not anonymous anymore
The anonymous Contact's UUID containing the fictional email address
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PIGGY_CREATE_CONTACT_ATTRIBUTETool to create a custom Contact Attribute. Use when you need to define new fields for contacts after initial setup.
Input parameters
Unique internal identifier for the Contact Attribute
Display label for the Contact Attribute
List of options for select or multi_select types. Each option has label and value
Data type of the attribute. Determines how values are validated and rendered
Human-readable description of the Contact Attribute
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PIGGY_CREATE_CREDIT_RECEPTIONTool to create a credit reception for a contact. Use when awarding credits to customers based on purchases or fixed amounts.
Input parameters
Fixed number of credits to award. Either unit_value or credits must be provided
UUID of the shop where the transaction occurred
Unit value (e.g., purchase amount in cents) for calculating credits. Either unit_value or credits must be provided
UUID of the contact to receive credits
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PIGGY_CREATE_VOUCHERS_BATCHTool to create a batch of vouchers for a promotion. Use when you need to generate multiple vouchers at once for a specific promotion. Batch processing is asynchronous and returns a PENDING status initially.
Input parameters
The number of Vouchers you want to generate (min: 1, max: 500)
The Contact's UUID to be linked to the batch of Vouchers
UUID of the Promotion for which the Vouchers are to be created
The activation date for the batch of Vouchers in ISO 8601 format
The expiration date for the batch of Vouchers in ISO 8601 format
Additional Custom Attributes for the Vouchers
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PIGGY_FIND_OR_CREATE_PRODUCTSTool to find an existing product by external_identifier or create a new one if it doesn't exist. Use when you need to ensure a product exists in Piggy's system for loyalty programs or rewards.
Input parameters
The name of the Product. Required when creating a new product
List of Categories that the product belongs to. Each category can be referenced by uuid or external_identifier
The description of the Product
A unique identifier from your system to find or create the product
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PIGGY_FIND_VOUCHER_BY_CODETool to find a voucher by its unique code. Use when you need to retrieve voucher details, check redemption status, or validate a voucher code.
Input parameters
The unique code of the Voucher, which serves as its identifier
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PIGGY_GET_CONTACT_AUTH_TOKENTool to get an auth token for a Contact. Use after obtaining a Contact UUID and needing to verify identity for secure operations.
Input parameters
UUID of the Contact for which to retrieve an auth token
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PIGGY_GET_CONTACTS_CREDIT_BALANCETool to get a Contact's credit balance. Use when you need to check a contact's current credit balance before processing rewards or promotions.
Input parameters
The UUID of the Contact for which to retrieve the credit balance
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PIGGY_LIST_FORMSTool to list all forms in the Piggy account. Use when you need to retrieve available forms for customer interactions.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PIGGY_LIST_PERKSTool to list all available perks in Piggy. Use when you need to retrieve the catalog of perks that can be associated with contacts or transactions.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PIGGY_MERGE_CONTACTSMerges a source contact into a destination contact in Piggy's CRM. The source contact's data (attributes, balances, transactions) is transferred to the destination contact, and the source contact is removed. This operation is irreversible and processed asynchronously via a job queue. Use this when consolidating duplicate customer records.
Input parameters
UUID of the source contact to merge. This contact will be removed after the merge, and all its data will be transferred to the destination contact.
UUID of the destination contact. This contact will remain active and receive all data from the source contact after the merge.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PIGGY_SEND_CONTACT_VERIFICATION_EMAILSend a verification email to a Piggy contact for identity verification. The contact must exist in the system with a configured Contacts Portal. Returns success message with email sent confirmation. Use this when implementing email-based authentication workflows or when contacts need to verify their email address to access the Contacts Portal.
Input parameters
Email address of the Contact to send the verification email to. The contact must already exist in the Piggy system.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PIGGY_UPDATE_BOOKINGSTool to update an existing booking in Piggy. Use when you need to modify booking details such as party size, status, or company name. Note: Shop and contact cannot be updated after creation.
Input parameters
Source from where the Booking was created
Booking status values.
The end date and time of the Booking in ISO 8601 format
The start date and time of the Booking in ISO 8601 format
External identifier for the Booking
The UUID of the Booking to update
Company name associated with the booking
The date and time when the party checked into the booking in ISO 8601 format
Amount prepaid (in cents) prior to booking start
Party size for the booking
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
PIGGY_UPDATE_CONTACT_IDENTIFIERSTool to update a contact identifier in Piggy. Use when you need to modify the display name or active state of an existing contact identifier. Only the name and active properties can be updated; the identifier value itself cannot be changed.
Input parameters
Display name of the contact identifier. Use this to update the human-readable label.
The unique value of the contact identifier to update. This is the identifier of the contact identifier record itself.
Active state of the contact identifier. Set to false to deactivate, true to activate.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 64 agents privately built on Nagent that already use Piggy.
Build on Nagent
Connect Piggy to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Piggy, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Piggy is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Piggy is connected, you configure its 14 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Piggy steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Piggy event fires, the agent kicks off automatically.
Every Piggy action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Piggy ships with 14 pre-built marketing automation actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Piggy together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Piggy-based workflows tailored to your business.