Connect Vouchery.io to Attentive

Both apps 28Vouchery.io 15Attentive 13

• Trigger
  New Voucher

  Triggers when a new voucher is created in the selected Vouchery campaign.

• Action
  Add campaign

  Creates a promo campaign in Vouchery — either a main campaign or a sub campaign under an existing main campaign — and returns the new campaign.

• Action
  Assign vouchers to customer

  Assigns one or more voucher codes to a customer and returns the customer's updated record.

• Action
  Cancel redemption

  Cancels a redemption by its redemption ID, marking it as cancelled.

• Action
  Confirm redemption

  Confirms a redemption so it counts toward the campaign's budget and total redemptions. Returns the confirmed redemption.

• Action
  Create Customer

  Creates a customer in Vouchery with their unique identifier, contact details, segment categories and metadata.

• Action
  Create Redemption

  Redeems a voucher code for a purchase, recording the order total or line items and returning the redemption with the discount and rewards granted.

• Action
  Delete customer

  Deletes a customer from your Vouchery project by their identifier.

• Action
  Find Voucher

  Finds a voucher by its code and returns its status, campaign, customer and redemption details.

• Action
  Get campaign

  Returns a single Vouchery campaign by its ID, including its rules, rewards, budget and voucher statistics.

• Action
  Get customer

  Returns a single customer by their identifier, including profile details, segments, loyalty points and voucher/redemption statistics.

• Action
  Get redemption

  Returns a single redemption by its ID, including its voucher, campaign, customer, confirmation status and granted rewards.

• Action
  List campaigns

  Returns the campaigns in your Vouchery project, optionally filtered by name, team, status, template or loyalty program.

• Action
  List customers

  Returns the customers in your Vouchery project, optionally filtered by identifier or email.

• Action
  Update customer

  Updates an existing customer's name, email, referral code, birthdate, segments or metadata. Only the values you provide are changed.

• Action
  Add to Cart

  Records that a shopper added a product to their cart in Attentive, so cart-abandonment journeys can fire.

• Action
  Custom Attributes

  Sets custom attributes (such as age, birthday or favorite team) on an Attentive user identified by phone, email, or external identifier.

• Action
  Custom Events

  Sends a custom event (such as "Order Shipped") for a user to Attentive, which can trigger Journeys.

• Action
  Delete Request

  Creates a privacy (CCPA) deletion request that deletes a subscriber within thirty days, identified by email, phone or client user id.

• Action
  Get Custom Attributes for a User

  Returns all custom attributes (name and value) stored on an Attentive user, looked up by phone number or email.

• Action
  Get Subscription Eligibility for a User

  Returns the subscription types and channels (SMS or email) a subscriber is eligible to receive messages on, looked up by phone number or email.

• Action
  Identity

  Associates a client user identifier or custom identifiers with an Attentive subscriber identified by phone, email, Shopify ID or Klaviyo ID.

• Action
  Lookup Product Catalog Ingestion

  Returns the status, validation errors and product counts of a product catalog upload.

• Action
  Product View

  Records that a shopper viewed one or more products in Attentive, so product-view journeys can fire.

• Action
  Purchase

  Records a purchase (order) event for a shopper in Attentive so it can trigger purchase-based journeys.

• Action
  Subscribe User

  Opts a person in to Attentive text or email subscriptions by phone or email, using a sign-up unit or a locale and subscription type.

• Action
  Unsubscribe Subscriptions for a User

  Unsubscribes a user (by phone or email) from specific Attentive subscription types and channels, or from all subscriptions when none are given.

• Action
  View Recent Catalog Uploads

  Returns your recent product catalog uploads with their ingestion status, product counts and validation errors, newest first.

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.