Connect PartnerStack to Attentive

Both apps 31PartnerStack 18Attentive 13

• Trigger
  New Application Event

  Triggers when a partner application is submitted or changes (for example, approved or declined).

• Trigger
  New Customer Event

  Triggers when a customer is created or updated in your PartnerStack program.

• Trigger
  New Deal Event

  Triggers when a deal is created or updated (for example, its stage, amount or close date changes).

• Trigger
  New Lead Event

  Triggers when a lead is created or updated (for example, approved, declined or closed).

• Trigger
  New Partnership Event

  Triggers when a partnership is created or updated in your PartnerStack program.

• Trigger
  New Reward Event

  Triggers when a reward is created or changes (for example, declined, restored or updated).

• Trigger
  New Transaction Event

  Triggers when a transaction is recorded or changes.

• Action
  Create Action

  Records an action a partner or customer performed (for example, posted in a forum), creating any reward tied to that action.

• Action
  Create Deal

  Creates a new deal attributed to the partner who registered it.

• Action
  Create Lead

  Creates a new lead attributed to the partner who referred it.

• Action
  Create Partner

  Creates a new partner (partnership) in your PartnerStack program and optionally emails them an invitation.

• Action
  Create Transaction

  Records a customer payment transaction so the referring partner is rewarded.

• Action
  Find Customer

  Looks up a customer by their customer key (or email) and returns their details.

• Action
  Find Lead

  Looks up a lead by its lead key and returns its details.

• Action
  Find Partner

  Finds a partner by their email address and returns the matching partnership.

• Action
  Update Customer

  Updates an existing customer's details, such as their name, email, or payment provider key.

• Action
  Update Deal

  Updates an existing deal, such as its stage, amount, or close date.

• Action
  Update Lead

  Updates an existing lead, such as its status, approval, or amount.

• 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.