Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Vouchery

Vouchery is a voucher and gift card management platform.

CategoryOther
Authenticationcustom
Version0.1.0
Published scopes0 published scopes
Last updatedSeptember 24, 2026

Overview

Connect Vouchery with Flows360

Vouchery is a voucher and gift card management platform.

Use the Vouchery connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 4 actions and no declared triggers.

Available actions

  • Create a voucher
  • Create Customer
  • Find Voucher
  • Custom API Call

Available triggers

  • No triggers are declared in this pinned package.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Vouchery
  • Package: @activepieces/piece-vouchery-io@0.1.0
  • Exact artifact digest: sha256:19b283565b1d9691683f01c4e3e86707ffe115cc7847dd05364e509289dd2a9d
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create a voucher (createAVoucher), Create a new voucher in a campaign Classification: read.
  • Create Customer (createCustomer), Create a new customer Classification: read.
  • Find Voucher (findVoucher), Find a voucher by campaign metadata. At least one metadata must be provided Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • No trigger delivery contracts are declared.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects4
Supported actions4
TriggersNone published

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Create a voucher Yes No Create a new voucher in a campaign
Create Customer Yes No Create a new customer
Find Voucher Yes No Find a voucher by campaign metadata. At least one metadata must be provided
Custom API Call Yes No Make a custom API call to a specific endpoint

Supported actions

Create a voucher · Read

Create a new voucher in a campaign

create_avoucher · Risk: low · Retry: safe

Inputs

  • campaignId · string · Required, Select the campaign
  • voucherCode · string · Required, The code for the voucher
  • voucher_valid_until · string · Optional, The date and time when the voucher expires
  • customer_identifier · number · Optional, The identifier for the customer
  • gift_card_value · number · Optional, The value of the gift card
  • activates_at · string · Optional, The date and time when the voucher becomes active
Create Customer · Read

Create a new customer

create_customer · Risk: low · Retry: safe

Inputs

  • identifier · string · Required, Unique customer identifier in your application. Can be hash, id, email or any other unique value
  • name · string · Optional, Customer full name
  • email · string · Optional, Customer email address
  • birthdate · object · Optional, Customer birthdate object
  • categories · array · Optional, Array of category objects to determine how customer is related to specific categories
  • metadata · object · Optional, Additional metadata for the customer
  • referrer_code · string · Optional, A referral code from the recommending user
  • loyalty_points · number · Optional, [DEPRECATED - use grant-points endpoint instead] Number of loyalty points customer will have
Find Voucher · Read

Find a voucher by campaign metadata. At least one metadata must be provided

find_voucher · Risk: low · Retry: safe

Inputs

  • purpose · string · Optional, Purpose metadata (multiple values allowed)
  • team · string · Optional, Team metadata (multiple values allowed)
  • channel · string · Optional, Channel metadata (multiple values allowed)
  • medium · string · Optional, Medium metadata (multiple values allowed)
  • customer_identifier · string · Optional, Optional: Assign the found voucher to a customer by providing their identifier
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Setup

Setup

  1. Add the Vouchery connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-vouchery-io@0.1.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 4 actions and 0 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Vouchery connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-vouchery-io@0.1.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com