PERSInstall

Summary

Adds a token unit to an existing PERS redemption by POSTing to /redemptions/{redemptionId}/tokens with the token entity, amount and optional limits.

Inputs

• Redemption ID (required) — UUID of the redemption to add the token unit to. It is inserted into the request URL and not sent in the body.
• Token Entity ID (required) — UUID of the token entity to add. Sent as tokenEntityId in the body. The field is masked in the UI.
• Amount (required) — Amount of tokens to mint or transfer. Defaults to 1. ERC721 is typically 1. ERC1155 and ERC20 can use any quantity.
• Additional Fields: Max Amount — Maximum amount of tokens a user can receive when acquiring the token unit. Useful for campaigns that grant token units per revenue spent.
• Additional Fields: Token Metadata Incremental ID — Token metadata template ID. For ERC1155 it becomes the on-chain tokenId. For ERC721 it is the lookup key for the template used to generate unique metadata.
• Additional Fields: Token ID (Deprecated) — Deprecated legacy identifier. Use Token Entity ID instead.

Output shape

One item per input item, containing the JSON response from the PERS API for the created redemption token unit.

The source doesn't show the response fields, so they depend on the API. The node authenticates with the persApi credential and uses its environment as the base URL. With Continue On Fail enabled, a failed item returns {error: message} instead of stopping the workflow. Body fields from Additional Fields are sent as set, so unset numeric fields may still be sent with their default of 0.

Examples

Example 1: Attach an ERC721 reward token to a new redemption

Redemption ID = the redemption UUID, Token Entity ID = the token UUID, Amount = 1, Token Metadata Incremental ID = the metadata template ID.

Example 2: Add a fungible token unit with a per-user cap

Amount = 100, Additional Fields > Max Amount = 500.

Links

• n8n community nodes installation guide