Connect PartnerStack and Yandex

Both apps 31PartnerStack 18Yandex 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.

• Trigger
  New file

  Triggers when a new file is uploaded to Yandex Disk.

• Action
  Add folder

  Creates a new empty folder at the given path on Yandex Disk. The parent folder must already exist.

• Action
  Copy resource

  Copies a file or folder on Yandex Disk to a new location and returns a link to the copy, or to the copy operation when Yandex performs it in the background.

• Action
  Delete resource

  Deletes a file or folder on Yandex Disk, moving it to the Trash by default or removing it permanently.

• Action
  Get disk info

  Returns general information about the connected user's Yandex Disk: total, used and trash space, file size limits, system folder paths and the disk owner.

• Action
  Get download link

  Returns a temporary direct link for downloading a file stored on Yandex Disk.

• Action
  Get resource

  Returns the details of a file or folder on Yandex Disk, such as its name, type, size, dates and custom properties. For a folder, the response also lists the items inside it.

• Action
  List files

  Returns a flat list of every file on the user's Yandex Disk, optionally filtered by media type and sorted.

• Action
  List public resources

  Returns the files and folders on your Yandex Disk that have been published with a public link.

• Action
  List recently uploaded files

  Returns the files most recently uploaded to Yandex Disk, newest first, optionally filtered by media type.

• Action
  Move resource

  Moves or renames a file or folder on Yandex Disk. Returns a link to the moved item, or to the background move operation when it runs asynchronously.

• Action
  Publish resource

  Publishes a file or folder on Yandex Disk so it gets a public link, optionally with access settings such as a password or expiry. Returns a link to the published resource's metadata.

• Action
  Update resource

  Adds or changes custom properties on a file or folder in Yandex Disk. Properties with the same name are overwritten, new ones are added, and a property set to null is removed.

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