Connect Wachete to Reepay

Both apps 29Wachete 9Reepay 20

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

• Action
  Add coupon

  Create a new coupon. POST /v1/coupon

• Action
  Add credit

  Create a credit note/credit for a customer. POST /v1/credit

• Action
  Add customer

  Create a new customer. POST /v1/customer

• Action
  Add invoice

  Create an invoice for a customer. POST /v1/customer/{handle}/invoice

• Action
  Add plan

  Create a new subscription plan. POST /v1/plan

• Action
  Add subscription

  Create a new subscription for a customer. POST /v1/subscription

• Action
  Cancel subscription

  Cancel a subscription by handle. POST /v1/subscription/{handle}/cancel

• Action
  Delete customer

  Delete a customer by handle. DELETE /v1/customer/{handle}

• Action
  Get charge

  Retrieve a charge by handle. GET /v1/charge/{handle}

• Action
  Get coupon

  Retrieve a coupon by handle. GET /v1/coupon/{handle}

• Action
  Get customer

  Retrieve a customer by handle. GET /v1/customer/{handle}

• Action
  Get invoice

  Retrieve an invoice by id. GET /v1/invoice/{id}

• Action
  Get plan

  Retrieve the current version of a plan by handle. GET /v1/plan/{handle}/current

• Action
  Get subscription

  Retrieve a subscription by handle. GET /v1/subscription/{handle}

• Action
  List customers

  List all customers. GET /v1/list/customer

• Action
  List invoices

  List all invoices. GET /v1/list/invoice

• Action
  List plans

  List all plans. GET /v1/list/plan

• Action
  List subscriptions

  List all subscriptions. GET /v1/list/subscription

• Action
  Update customer

  Update an existing customer by handle. PUT /v1/customer/{handle}

• Action
  Update subscription

  Change/update an existing subscription by handle. PUT /v1/subscription/{handle}

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