Connect Adyen and Wachete

Both apps 20Adyen 11Wachete 9

• Trigger
  New refund

  Webhook REFUND: result of refund request.

• Action
  Add payment

  Starts a payment (authorisation) in Adyen Checkout for the given amount, payment method and merchant account, and returns the payment's PSP reference and result code.

• Action
  Add payment link

  Creates an Adyen Pay by Link payment link that a shopper can open to pay the given amount.

• Action
  Cancel payment

  Cancels an authorised payment that has not been captured yet, releasing the funds back to the shopper. The final outcome arrives later in Adyen's CANCELLATION webhook.

• Action
  Capture payment

  Captures an authorised payment (full or partial amount). Adyen processes the capture asynchronously: the response always has status "received" and the final outcome arrives later in a CAPTURE webhook.

• Action
  Delete stored payment method

  Deletes (disables) a shopper's stored payment details token in Adyen.

• Action
  Get payment link

  Retrieves the details of a payment link, including its amount, status (active, completed, expired or paymentPending), url and expiry.

• Action
  List payment methods

  Retrieves the payment methods available for a transaction, based on details such as amount, country and currency, plus the shopper's stored payment methods when a shopper reference is given.

• Action
  List stored payment methods

  Lists the tokens for payment details stored for a shopper, with a summary of each stored card or account.

• Action
  Refund payment

  Refunds a captured Adyen payment, fully or partially. Adyen acknowledges the request immediately; the final outcome arrives later in a REFUND notification.

• Action
  Update payment link

  Updates the status of an Adyen payment link. Adyen only allows setting the status to expired, which forces the link to expire so shoppers can no longer pay with it.

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