Connect PartnerStack and Wachete

Both apps 27PartnerStack 18Wachete 9

• 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
  Any new notification

  Fires when there is a new change notification from any monitor in your Wachete account.

• Trigger
  New notification for monitor

  Fires when there is a new change notification from the specified Wachete monitor (taskId).

• Action
  Create monitor

  Create a new Wachete monitor (wachet) that watches a web page or part of a page for changes.

• Action
  Delete monitor

  Delete a Wachete monitor by its ID.

• Action
  Get monitor

  Get information about a specific Wachete monitor by its ID.

• Action
  Get monitor data

  Get the captured data/history for a Wachete monitor, optionally as a diff and within a date range.

• Action
  List folders

  List folder contents, optionally under a parent folder.

• Action
  List notifications

  List change notifications, optionally filtered by monitor (taskId) and date range.

• Action
  Update monitor

  Change the settings of an existing Wachete monitor — name, URL, watched/excluded XPath, regex, note, job type, check frequency and location, crawl options, folder, alerts, notification endpoints, headers and proxies. A partial update: the op first reads the monitor's current record, overlays only the fields you filled in, then writes the merged record back, so anything you leave blank keeps its current value — including settings this op does not expose. Identify the monitor by its id. Check frequency is in seconds (86400 = daily) and is ignored if not positive; the true/false options take the words true or false; alerts, notification endpoints, headers and proxies take JSON. Returns the monitor id, name and URL after the update plus the full monitor record.

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